Yep, Rob's correct, that's the intent. There's also plenty of non-WIP high priority patches in the starred list :-)
On 16 December 2016 at 23:31, Rob Cresswell (rcresswe) <rcres...@cisco.com> wrote: > I think the intent is to get eyes on those patches, to prevent a 1000 line > rewrite only for a core to say “I think this is a bad idea”. So for > important patches, its probably good to get earlier feedback. > > Rob > > > On 16 Dec 2016, at 08:13, Radomir Dopieralski <openst...@sheep.art.pl> > wrote: > > I wonder if it really makes sense to put WIP patches on the priority list. I > think it's a bit counter-productive, considering that the prioritizing of > patches was supposed to make them merge faster -- but we don't want to merge > WIP patches, do we? > > On Fri, Dec 16, 2016 at 5:31 AM, Richard Jones <r1chardj0...@gmail.com> > wrote: >> >> Hi folks, >> >> No Horizon meeting next week! I'll be around the week after (28th >> December) so if anyone else is around we can totally have a meeting >> then. >> >> Things that have happened this week, including in the team meeting[1] >> >> Ocata-2 was tagged! >> >> xstatic-angular-bootstrap 2.2.0.0 was released, which promptly broke >> Ocata-2 (and Ocata-1, you're welcome). We knew it was coming, and Rob >> Cresswell had a compatibility patch in place ready to go, so master >> was back to working within half an hour of the upper-constraints patch >> enabling 2.2.0.0! If you notice anything busted in Horizon related to >> bootstrap please file a bug! >> >> I'd like to remind everyone that we have a blueprint in play which >> describes our approach to API microversions[2]. Rob has a patch which >> will land imminently that implements the core of the design. Please >> hold off implementing your own version settings/checks! We've seen a >> few microversion-related patches appear recently, and that's great to >> see, we just need to make sure we're all heading in the same >> direction. >> >> I've put up the first patch using ui-router which rather dramatically >> alters the Swift UI[3], so I'd like some feedback on it please. >> >> We've got about five(ish) weeks until Feature Freeze[4], folks, so all >> the help we can get on the priority patches[5] (reviews or coding >> help) is appreciated! >> >> >> I hope you all get to have some time off, and have an enjoyable holiday, >> >> Richard >> >> [1] >> http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-12-14-20.00.html >> [2] https://blueprints.launchpad.net/horizon/+spec/microversion-support >> [3] https://review.openstack.org/#/c/350523 >> [4] https://releases.openstack.org/ocata/schedule.html >> [5] >> https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open >> >> __________________________________________________________________________ >> 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 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 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 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