[openstack-dev] [requirements][infra] Maintaining constraints for several python versions

Tony Breeds tony at bakeyournoodle.com
Thu Jul 12 23:55:50 UTC 2018

On Thu, Jul 12, 2018 at 01:52:56PM +0000, Jeremy Stanley wrote:
> On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote:
> [...]
> > I think most of the problems with Fedora stability are around
> > bringing up a new Fedora every 6 months or so. They tend to change
> > sufficiently within that time period to make this a fairly
> > involved exercise. But once working they work for the ~13 months
> > of support they offer. I know Paul Belanger would like to iterate
> > more quickly and just keep the most recent Fedora available
> > (rather than ~2).
> [...]
> Regardless its instability/churn makes it unsuitable for stable
> branch jobs because the support lifetime of the distro release is
> shorter than the maintenance lifetime of our stable branches. Would
> probably be fine for master branch jobs but not beyond, right?

Yup we only run the generate job on master, once we branch it's up to
poeple to update/review the lists.  So I'd hope that we'd have f28 and
f29 overlap and roll forward as needed/able

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/20180713/fa6975f3/attachment.sig>

More information about the OpenStack-dev mailing list