March 2019 - openstack-discuss - lists.openstack.org

Re: networking-powervm 8.0.0.0rc1 (stein)
by James LaBarre 22 Mar '19

22 Mar '19

On 3/21/19 1:39 PM, no-reply(a)openstack.org wrote: > Hello everyone, > > A new release candidate for networking-powervm for the end of the Stein > cycle is available! You can find the source code tarball at: > > ... > Release notes for networking-powervm can be found at: > > https://docs.openstack.org/releasenotes/networking-powervm/ Just FYI, the links for this and the ceilometer-powervm release nodes don't work.

2 1

[tc][infra] When a project leaves OpenStack
by Jeremy Stanley 22 Mar '19

22 Mar '19

This is a discussion I've been meaning to start for a very, very long while. The tl;dr of it is that when official OpenStack projects have ceased to meet our expectations for what it means to be OpenStack, allowing them to continue on in an unofficial capacity but otherwise unchanged has led to confusion among users. Finding a better way to handle project removals is my goal for this conversation. Inevitably, there are times when projects cannot continue to be a part of OpenStack. Often this is because development has ceased, and so we can retire their repositories cleanly leaving a notice to any remaining users that the project is unmaintained. Sometimes a project is unable or unwilling to continue to be a part of OpenStack officially, and we have made the choice to simply remove them from our governance but otherwise wish them well on their new journey. Unfortunately, more often than not, a formerly official project continuing development outside OpenStack is an indication it's nearing the end of its life, soon thereafter ceasing development and leaving behind an abandoned repository where even the most critical bugs go untriaged and proposed fixes unreviewed. This is the case for a lot of software which has ceased viability, so unsurprising, but given it was once a part of OpenStack there are users who simply assume it's still maintained and so it reflects negatively on us when they end up having a bad experience. One possibility we've entertained, over the years this topic has cropped up, is to declare that projects in the infrastructure we share (soon to be known as OpenDev) which were once an official part of OpenStack retain some residual TC jurisdiction so that if we notice their maintainers have disappeared we can take over and close down the project more thoroughly. This may work well enough in situations where it's brought to our attention, but will clearly not help the first people to notice this situation nor does it help in cases where we're never informed. With the "namespace explosion" coming in OpenDev, however, there's another option open to us. We could require that any development which continues after removal from OpenStack be done as a fork of the original. In theory we could have done that even with one common namespace, by requiring projects to either cease using this infrastructure entirely or change their name. Neither of these options is especially desirable. Now, however, we might consider allowing them to continue in the same infrastructure under the same repository name but in a different namespace. We would effectively close down development on the original repository following our normal retirement process, but could optionally also include a note mentioning where continued development is known to be taking place instead. Does anyone have other ideas to suggest? -- Jeremy Stanley

3 3

masakari-monitors 7.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for masakari-monitors for the end of the Stein 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 Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/masakari-monitors/log/?h=stable/st… 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: http://bugs.launchpad.net/masakari-monitors and tag it *stein-rc-potential* to bring it to the masakari-monitors release crew's attention.

1 0

masakari 7.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

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

1 0

panko 6.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

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

1 0

aodh 8.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for aodh for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/aodh/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/aodh/log/?h=stable/stein Release notes for aodh can be found at: https://docs.openstack.org/releasenotes/aodh/

1 0

trove-dashboard 12.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for trove-dashboard for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/trove-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/trove-dashboard/log/?h=stable/stein Release notes for trove-dashboard can be found at: https://docs.openstack.org/releasenotes/trove-dashboard/

1 0

trove 11.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for trove for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/trove/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/trove/log/?h=stable/stein Release notes for trove can be found at: https://docs.openstack.org/releasenotes/trove/

1 0

glance 18.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for glance for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/glance/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/glance/log/?h=stable/stein Release notes for glance can be found at: https://docs.openstack.org/releasenotes/glance/

1 0

[dev][cinder][stable-maint] python-cinderclient stein catch-up
by Brian Rosmaita 22 Mar '19

22 Mar '19

This is mainly addressed to the cinder stable-maint cores. As Eric noticed at the last Cinder team meeting, while we have had a Stein cycle python-cinderclient release (4.1.0), it was back in October [0]. Because we didn't do another more recent release including the patches that had collected in master, the stable/stein branch was cut at the 4.1.0 tag, and thereby missed some bugfixes. (We don't seem to have missed any major functionality, however.) I've put together an etherpad of the "missing" patches [1]. It notes the patches I think it's OK to skip and it notes a few dependencies among patches. If any of those look like they should be included, feel free to propose a backport. I've put up backports to stable/stein with the topic "stein-ketchup" for the rest. There are some that we probably wouldn't normally consider, but this is a bit of an unusual case if we want stable/stein to look the way it would have if we'd cut a release 2 weeks ago. Feel free to -2, I won't take it personally, I just figured it would be faster to make the decision on the reviews rather than try to figure it out up front. Please review at your earliest convenience: https://review.openstack.org/#/q/topic:stein-ketchup+(status:open+OR+status… cheers, brian [0] http://git.openstack.org/cgit/openstack/python-cinderclient/tag/?h=4.1.0 [1] https://etherpad.openstack.org/p/cinderclient-master-20-march

3 2