On 06/11/2018 11:53 AM, Thierry Carrez wrote:
> Hi everyone,
>
> As some of the OpenStack deliverables get more mature, we need to adjust
> our release policies to best handle the case of deliverables that do not
> need to be updated that much. This discussion started with how to handle
> those
Option 2 for me. And the option switch to independant is IMO just fine.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
Excerpts from Zane Bitter's message of 2018-06-12 17:52:24 -0400:
> On 12/06/18 11:41, Michael Johnson wrote:
> > I think we should continue with option 1.
> >
> > It is an indicator that a project is active in OpenStack and is
> > explicit about which code should be used together.
> >
> > Both
On 12/06/18 11:41, Michael Johnson wrote:
I think we should continue with option 1.
It is an indicator that a project is active in OpenStack and is
explicit about which code should be used together.
Both of those statements hold no technical water, but address the
"human" factor of "What is
Excerpts from Michael Johnson's message of 2018-06-12 08:41:57 -0700:
> I think we should continue with option 1.
>
> It is an indicator that a project is active in OpenStack and is
> explicit about which code should be used together.
>
> Both of those statements hold no technical water, but
On Mon, Jun 11, 2018 at 2:53 AM, Thierry Carrez wrote:
>
> 2bis/ Like 2, but only create the branch when needed
>
> Same as the previous one, except that rather than proactively create the
> stable branch around release time, we'd wait until the branch is actually
> needed to create it.
>
This
I think we should continue with option 1.
It is an indicator that a project is active in OpenStack and is
explicit about which code should be used together.
Both of those statements hold no technical water, but address the
"human" factor of "What is OpenStack?", "What do I need to deploy?",
Excerpts from Thierry Carrez's message of 2018-06-11 11:53:52 +0200:
> Hi everyone,
>
> As some of the OpenStack deliverables get more mature, we need to adjust
> our release policies to best handle the case of deliverables that do not
> need to be updated that much. This discussion started
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
Hi everyone,
As some of the OpenStack deliverables get more mature, we need to adjust
our release policies to best handle the case of deliverables that do not
need to be updated that much. This discussion started with how to handle
those "stable" libraries, but is actually also relevant for
10 matches
Mail list logo
