Open Stack

On Tue, Jun 26, 2018 at 09:03:40AM -0400, Doug Hellmann wrote:
> Requirements team,
> 
> At some point in the next few months we're going to want to raise
> the constraint on openstackdocstheme in all of the old branches so
> we can take advantage of a new feature for showing the supported
> status of each version of a project. That feature isn't implemented
> yet, but I thought it would be good to discuss in advance the need
> to update the dependency and how to do it.
> 
> The theme is released under an independent release model and does
> not currently have stable branches.  It depends on pbr and dulwich,
> both of which should already be in the requirements and constraints
> lists (dulwich is a dependency of reno).

The only possible gottcha is if openstackdocstheme relies on a feature
in any of pbr or dulwich which isn't in the version currently in
upper-constratints.txt.  If that happens we can easily bump those
constraints also.
 
> I think that means the simplest thing to do would be to just update
> the constraint for the theme in the stable branches. Does that seem
> right?

Yup that seems to be all there is to it.  Once the release happens the
bot will propose the constraints bump on master which someone will need
to cherry-pick onto the stable branches.

Yours Tony.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180627/a9689ab3/attachment.sig>