September 2019 - openstack-discuss

masakari-dashboard 1.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for masakari-dashboard for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/masakari-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/masakari-dashboard/src/branch/stable/train Release notes for masakari-dashboard can be found at: https://docs.openstack.org/releasenotes/masakari-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/masakari/+bugs and tag it *train-rc-potential* to bring it to the masakari-dashboard release crew's attention.

1 0

masakari-monitors 8.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for masakari-monitors for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/masakari-monitors/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/masakari-monitors/src/branch/stable/train Release notes for masakari-monitors can be found at: https://docs.openstack.org/releasenotes/masakari-monitors/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/masakari-monitors/+bugs and tag it *train-rc-potential* to bring it to the masakari-monitors release crew's attention.

1 0

designate-dashboard 9.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for designate-dashboard for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/designate-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/designate-dashboard/src/branch/stable/train Release notes for designate-dashboard can be found at: https://docs.openstack.org/releasenotes/designate-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/designate-dashboard/+bugs and tag it *train-rc-potential* to bring it to the designate-dashboard release crew's attention.

1 0

senlin 8.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for senlin for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/senlin/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/senlin/src/branch/stable/train Release notes for senlin can be found at: https://docs.openstack.org/releasenotes/senlin/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/senlin/+bugs and tag it *train-rc-potential* to bring it to the senlin release crew's attention.

1 0

magnum 9.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for magnum for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/magnum/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/magnum/src/branch/stable/train Release notes for magnum can be found at: https://docs.openstack.org/releasenotes/magnum/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/magnum/+bugs and tag it *train-rc-potential* to bring it to the magnum release crew's attention.

1 0

heat-dashboard 2.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for heat-dashboard for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/heat-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/heat-dashboard/src/branch/stable/train Release notes for heat-dashboard can be found at: https://docs.openstack.org/releasenotes/heat-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/heat-dashboard/+bugs and tag it *train-rc-potential* to bring it to the heat-dashboard release crew's attention.

1 0

[release] Release countdown for week R-2, September 30 - October 4
by Sean McGinnis 27 Sep '19

27 Sep '19

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the Train deliverables. Teams should be working on any release critical bugs that would require another RC or intermediary release before the final release. Actions ---------- Early in the week, the release team will be proposing stable/train branch creation for all deliverables that have not branched yet, using the latest available Train release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/train branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/train branch before releasing out of the stable/train branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for Ussuri development, though the focus should still be on finishing up Train until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final Train release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targetted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the Train version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: October 10 (R-1 week) Final Train release: October 16 Forum+PTG at Shanghai summit: November 4

1 0

blazar 4.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for blazar for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/blazar/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/blazar/src/branch/stable/train Release notes for blazar can be found at: https://docs.openstack.org/releasenotes/blazar/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/blazar/+bugs and tag it *train-rc-potential* to bring it to the blazar release crew's attention.

1 0

[release][ptl] RC1 Deadline Approaching
by Sean McGinnis 27 Sep '19

27 Sep '19

Hey everyone, Just a reminder that we are hours away from the end of the planned RC1 deadline. There are still quite a few projects that have not done an RC yet. We really could use everyone's help to make this go smoothly. JP was able to generate a set of RC patches for all projects. They can be found here: https://review.opendev.org/#/q/status:open+project:openstack/releases+branc… If you are ready for the RC release, please indicate so by leaving a +1 on the patch so the release team knows it is safe to go ahead with processing the release request. If you are still trying to get some last minute things through the gate, it would also help us if you left a -1 on the release patch with any comments that can help us gauge how long we need to wait yet to do the release. Of course, if you are ready but there have been commits merged since the autogeneration of the patch, please update it with the right commit hash to use. The release, and the stable/train branch, will be created off of this point. One final thing to keep in mind - this is just the initial RC for train. We have a couple weeks to do an RC2 (or even RC3 if needed) so if you are waiting on a few nice to have bugfixes, it is still possible to get those in even if it looks like they will take a little longer. But also keep in mind that with the stable/train branch creation on RC1, those would also need to be backported after merging to master (ussuri) at this point. Thanks for your help as we try to get the train out. Sean

1 1

[openstack-ansible] office hours update
by Mohammed Naser 27 Sep '19

27 Sep '19

Hi everyone, Here’s an update of what happened in this week’s OpenStack Ansible Office Hours. We combined the ironic and inspector virtual environments. The ironic patch needs to be reviewed. We didn’t have much activity because a bunch of us were at AnsibleFest. Thanks for tuning in! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0