On 17/11/15 13:38, Alan Pevec wrote:
2015-11-12 21:37 GMT+01:00 Zane Bitter <[email protected]>:
https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:stable/juno,n,z

It would be nice to treat the remaining 'High' priority one as a blocker.
The rest aren't a blocker for the release but it would be really nice to at
least have time to get them all backported and merged before the stable
branch gets deleted.

There are still quite a few open reviews for Heat Juno, please tell us
which should be merged as freeze exceptions, because immediately after
freeze Juno goes EOL!

* https://review.openstack.org/245368 Medium
https://bugs.launchpad.net/heat/+bug/1424600
* https://review.openstack.org/245373 Medium
https://bugs.launchpad.net/heat/+bug/1424899
* https://review.openstack.org/246113 Medium
https://bugs.launchpad.net/heat/+bug/1471135
* https://review.openstack.org/244957 Medium
https://bugs.launchpad.net/heat/+bug/1418935
* https://review.openstack.org/246192 High
https://bugs.launchpad.net/heat/+bug/1508096
* https://review.openstack.org/246163 Undecided
https://bugs.launchpad.net/heat/+bug/1419693

This is not the last of them either.

I don't want to hold up the release for everybody. We got the High-priority fixes from Kilo that had been languishing on the backlog in already.

It's nice to get patches merged, but the more important thing is to get reviews up because distributors can always grab patches from reviews, but once the branch is deleted and there are no more Jenkins tests we lose the ability to collaborate in any meaningful way on backports, and everybody is on their own. That's what we're trying to focus on at the moment.

cheers,
Zane.

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to