[openstack-dev] We should move strutils.mask_password back into oslo-incubator
davanum at gmail.com
Wed Oct 7 20:00:18 UTC 2015
My vote is for #1, as we should kill oslo-incubator in Mitaka.
On Wed, Oct 7, 2015 at 3:38 PM, Matt Riedemann <mriedem at linux.vnet.ibm.com>
> Here's why:
> That's marked as fixing an OSSA which means we'll have to backport the fix
> in nova but it depends on a change to strutils.mask_password in oslo.utils,
> which required a release and a minimum version bump in global-requirements.
> To backport the change in nova, we either have to:
> 1. Copy mask_password out of oslo.utils and add it to nova in the backport
> 2. Backport the oslo.utils change to a stable branch, release it as a
> patch release, bump minimum required version in stable g-r and then
> backport the nova change and depend on the backported oslo.utils stable
> release - which also makes it a dependent library version bump for any
> packagers/distros that have already frozen libraries for their stable
> releases, which is kind of not fun.
> So I'm thinking this is one of those things that should ultimately live in
> oslo-incubator so it can live in the respective projects. If mask_password
> were in oslo-incubator, we'd have just fixed and backported it there and
> then synced to nova on master and stable branches, no dependent library
> version bumps required.
> Plus I miss the good old days of reviewing oslo-incubator syncs...(joking
> of course).
> Matt Riedemann
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Davanum Srinivas :: https://twitter.com/dims
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev