[ptl][release] Last call for RC updates
Hey everyone, This is just a reminder about tomorrow's deadline for a final RC for Train. There are several projects that have changes merged since cutting the stable/train branch. Not all of these changes need to be included in the initial Train coordinated release, but it would be good if there are translations and bug fixes merged to get them into a final RC while there's still time. After tomorrow's (Oct 10) deadline, we will only want to release something if it's absolutely critical. We will enter a quiet period from tomorrow until the coordinated release date next week to give time for packagers to complete their work and to make sure things are stable. Next week the last RC releases will then be retagged as the final release. Again, not all changes need to be included if they are not critical bugfixes or translations at this point. Stable releases can be done at any point after the official release date. Thanks for your help as we reach the end of the Train. Sean
On Wed, Oct 09, 2019 at 08:44:11AM -0500, Sean McGinnis wrote:
Hey everyone,
This is just a reminder about tomorrow's deadline for a final RC for Train.
There are several projects that have changes merged since cutting the stable/train branch. Not all of these changes need to be included in the initial Train coordinated release, but it would be good if there are translations and bug fixes merged to get them into a final RC while there's still time.
To try to help some teams, I have proposed RC2 releases for those deliverables that looked like they had relevant things that would be good to pick up for the final Train release. They can be found under the train-rc2 topic: https://review.opendev.org/#/q/topic:train-rc2+(status:open+OR+status:merged) Again, not all changes are necessary to be included, so we will only process these if we get an explicit ack from the PTL or release liaison that the team actually wants these extra RC releases. Feel free to +1 if you would like us to proceed, or -1 if you do not want the RC or just need a little more time to get anything else merged before tomorrow's deadline. If the latter, please take over the patch and update with the new commit hash that should be used for the release. Thanks! Sean
Hi,
On 9 Oct 2019, at 17:46, Sean McGinnis <sean.mcginnis@gmx.com> wrote:
On Wed, Oct 09, 2019 at 08:44:11AM -0500, Sean McGinnis wrote:
Hey everyone,
This is just a reminder about tomorrow's deadline for a final RC for Train.
There are several projects that have changes merged since cutting the stable/train branch. Not all of these changes need to be included in the initial Train coordinated release, but it would be good if there are translations and bug fixes merged to get them into a final RC while there's still time.
To try to help some teams, I have proposed RC2 releases for those deliverables that looked like they had relevant things that would be good to pick up for the final Train release. They can be found under the train-rc2 topic:
https://review.opendev.org/#/q/topic:train-rc2+(status:open+OR+status:merged)
Thx a lot for doing this Sean :)
Again, not all changes are necessary to be included, so we will only process these if we get an explicit ack from the PTL or release liaison that the team actually wants these extra RC releases.
Feel free to +1 if you would like us to proceed, or -1 if you do not want the RC or just need a little more time to get anything else merged before tomorrow's deadline. If the latter, please take over the patch and update with the new commit hash that should be used for the release.
Thanks! Sean
— Slawek Kaplonski Senior software engineer Red Hat
participants (2)
-
Sean McGinnis
-
Slawek Kaplonski