Re: [openstack-dev] [release][requirements] FFE release for reno 2.5.0
On 17-08-02 23:18:19, Tony Breeds wrote: > On Wed, Aug 02, 2017 at 08:39:07AM -0400, Doug Hellmann wrote: > > We have a few projects that have modified stable branch release > > notes by editing the files on master, which makes those notes appear > > as part of the current release. Reno has a new option to address > > that problem by ignoring some note files, and I would like to release > > that version to allow project teams to fix up their release notes > > for pike. I really thought I had already released that update, so > > I'm sorry for the late request. > > > > Reno is only used during release notes builds, but it does appear > > in the global requirements list and constraints list. I think the > > risk is minimal. > > > > https://review.openstack.org/489998 > > Package : reno [reno!=2.3.1,>=1.8.0] (used by 220 projects) > Also affects : 220 projects > > > So yeah it *could* destabalise the gate for a day if there is an issue. > I'm not saying that's likely but it has happened in the past. > > Looking at the reno change log I don't see anything that worries me. > > From a requirements POV I'm +2 on a u-c bump -2 on a g-r bump. > > Yours Tony. Agreed, the amount of projects that'd be impacted by a GR bump is too high, but a UC bump is fine. -- Matthew Thode (prometheanfire) signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [release][requirements] FFE release for reno 2.5.0
On Wed, Aug 02, 2017 at 08:39:07AM -0400, Doug Hellmann wrote: > We have a few projects that have modified stable branch release > notes by editing the files on master, which makes those notes appear > as part of the current release. Reno has a new option to address > that problem by ignoring some note files, and I would like to release > that version to allow project teams to fix up their release notes > for pike. I really thought I had already released that update, so > I'm sorry for the late request. > > Reno is only used during release notes builds, but it does appear > in the global requirements list and constraints list. I think the > risk is minimal. > > https://review.openstack.org/489998 Package : reno [reno!=2.3.1,>=1.8.0] (used by 220 projects) Also affects : 220 projects So yeah it *could* destabalise the gate for a day if there is an issue. I'm not saying that's likely but it has happened in the past. Looking at the reno change log I don't see anything that worries me. From a requirements POV I'm +2 on a u-c bump -2 on a g-r bump. Yours Tony. signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [release][requirements] FFE release for reno 2.5.0
Doug Hellmann wrote: > We have a few projects that have modified stable branch release > notes by editing the files on master, which makes those notes appear > as part of the current release. Reno has a new option to address > that problem by ignoring some note files, and I would like to release > that version to allow project teams to fix up their release notes > for pike. I really thought I had already released that update, so > I'm sorry for the late request. > > Reno is only used during release notes builds, but it does appear > in the global requirements list and constraints list. I think the > risk is minimal. > > https://review.openstack.org/489998 Sounds like something we should fix before release rather than after, so +2 from me. -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release][requirements] FFE release for reno 2.5.0
We have a few projects that have modified stable branch release notes by editing the files on master, which makes those notes appear as part of the current release. Reno has a new option to address that problem by ignoring some note files, and I would like to release that version to allow project teams to fix up their release notes for pike. I really thought I had already released that update, so I'm sorry for the late request. Reno is only used during release notes builds, but it does appear in the global requirements list and constraints list. I think the risk is minimal. https://review.openstack.org/489998 Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
