[openstack-dev] [all] [release] How to handle "stable" deliverables releases
Chris Dent
cdent+os at anticdent.org
Mon Jun 11 12:47:30 UTC 2018
On Mon, 11 Jun 2018, Thierry Carrez wrote:
> 2/ Do not force releases, but still create branches from latest releases
>
> In this variant we would not force an artificial re-release, but we would
> still create a branch from the last available release, in order to be able to
> land future patches and do bugfix or security releases as needed.
This one seems best because of:
> creating
> the branches in advance means they are ready to be used when someone wants to
> backport something there, likely reducing process pain.
Really glad to see this happening. We need to make sure that we
don't accidentally make low-activity because mature and stable look
the same as low-activity because dead.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent
More information about the OpenStack-dev
mailing list