[openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

Ihar Hrachyshka ihrachys at redhat.com
Mon Oct 19 08:49:48 UTC 2015

> On 16 Oct 2015, at 13:02, Victor Stinner <vstinner at redhat.com> wrote:
> Le 15/10/2015 17:54, Joshua Harlow a écrit :
>> I had this problem with deprecation versioning (the debtcollector
>> library functions take a version="XYZ", removal_version="ABC" params,
>> see
>> http://docs.openstack.org/developer/debtcollector/examples.html#further-customizing-the-emitted-messages)
>> and it is pretty hard to get those two numbers right, especially with
>> weekly releases and not knowing when a review will merge... I'm not
>> saying we shouldn't try to do this, but we just have to figure out how
>> to do it in a smart way.
> I hope that we will not release *too* frequently. Oslo libraries are supposed to be somehow "stable" :-) Past history showed that any minor change has major impact on the OpenStack CI ;-)

Once we have all major gate jobs using constraints file from openstack/requirements, we should not affect CI and hence development pace. I think neutron gate is quite close to that goal (we already have -constraints jobs for pep8/doc/py* jobs), and I believe other projects should follow the lead.

Once we are there, no oslo release should break the world. That of course does not mean we can release breaking changes, but it should make mistakes less painful.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151019/3f2b4e50/attachment.pgp>

More information about the OpenStack-dev mailing list