settingsLogin | Registersettings

[openstack-dev] [all] creating stable branches for all libraries, Oslo, client, and other

0 votes

We have a cross-project spec up for review discussing a change in the release process precipitated by the fact that we are now capping library versions in stable branch test configurations. We’ve talked about it a couple of times at the cross-project meetings, but we also want to make sure it is widely seen because it will affect the way bug fixes need to be managed in client libraries (new releases of clients won’t automatically make it into stable branches, and we will need to maintain stable branches of the clients with back-ports for critical fixes).

The Oslo team has already followed this procedure, including releasing some versions of libraries with backports for the stable branches. I think most of the wrinkles are therefore worked out, and I would like to move ahead with this for all projects that release library-like artifacts for Kilo, understanding that we might need to update the document, procedures, and tools as we go.

Please take a few minutes to read the spec: https://review.openstack.org/#/c/155072/

Thanks,
Doug


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Mar 24, 2015 in openstack-dev by Doug_Hellmann (87,520 points)   3 4 9
retagged Apr 14, 2015 by admin

3 Responses

0 votes

On Tue, Mar 24, 2015 at 1:13 PM, Doug Hellmann doug@doughellmann.com
wrote:

We have a cross-project spec up for review discussing a change in the
release process precipitated by the fact that we are now capping library
versions in stable branch test configurations. We’ve talked about it a
couple of times at the cross-project meetings, but we also want to make
sure it is widely seen because it will affect the way bug fixes need to be
managed in client libraries (new releases of clients won’t automatically
make it into stable branches, and we will need to maintain stable branches
of the clients with back-ports for critical fixes).

Here is a real case where the correct fix is a stable branch for a client:
https://bugs.launchpad.net/python-glanceclient/+bug/1423165

The Oslo team has already followed this procedure, including releasing
some versions of libraries with backports for the stable branches. I think
most of the wrinkles are therefore worked out, and I would like to move
ahead with this for all projects that release library-like artifacts for
Kilo, understanding that we might need to update the document, procedures,
and tools as we go.

Please take a few minutes to read the spec:
https://review.openstack.org/#/c/155072/

Thanks,
Doug


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 24, 2015 by Joe_Gordon (24,620 points)   2 5 8
0 votes

Excerpts from Joe Gordon's message of 2015-03-24 14:22:03 -0700:

On Tue, Mar 24, 2015 at 1:13 PM, Doug Hellmann doug@doughellmann.com
wrote:

We have a cross-project spec up for review discussing a change in the
release process precipitated by the fact that we are now capping library
versions in stable branch test configurations. We’ve talked about it a
couple of times at the cross-project meetings, but we also want to make
sure it is widely seen because it will affect the way bug fixes need to be
managed in client libraries (new releases of clients won’t automatically
make it into stable branches, and we will need to maintain stable branches
of the clients with back-ports for critical fixes).

Here is a real case where the correct fix is a stable branch for a client:
https://bugs.launchpad.net/python-glanceclient/+bug/1423165

That's a great concrete example, Joe, thanks.

Doug

The Oslo team has already followed this procedure, including releasing
some versions of libraries with backports for the stable branches. I think
most of the wrinkles are therefore worked out, and I would like to move
ahead with this for all projects that release library-like artifacts for
Kilo, understanding that we might need to update the document, procedures,
and tools as we go.

Please take a few minutes to read the spec:
https://review.openstack.org/#/c/155072/

Thanks,
Doug


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 25, 2015 by Doug_Hellmann (87,520 points)   3 4 9
0 votes

Am 24/03/15 um 22:22 schrieb Joe Gordon:

On Tue, Mar 24, 2015 at 1:13 PM, Doug Hellmann doug@doughellmann.com
wrote:

We have a cross-project spec up for review discussing a change in the
release process precipitated by the fact that we are now capping library
versions in stable branch test configurations. We’ve talked about it a
couple of times at the cross-project meetings, but we also want to make
sure it is widely seen because it will affect the way bug fixes need to be
managed in client libraries (new releases of clients won’t automatically
make it into stable branches, and we will need to maintain stable branches
of the clients with back-ports for critical fixes).

Here is a real case where the correct fix is a stable branch for a client:
https://bugs.launchpad.net/python-glanceclient/+bug/1423165

In case someone would like to read a bit about how this bug manifested
itself for us from an operators point of view:

http://blog.offenerstapel.de/blog/2015/03/25/openstack-gone-wild/


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 25, 2015 by Dr._Jens_Rosenboom (1,680 points)   3
...