Open Stack

-----Original Message-----
From: Brian Rosmaita <rosmaita.fossdev at gmail.com>
Reply: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Date: December 14, 2016 at 14:18:23
To: openstack-dev at lists.openstack.org <openstack-dev at lists.openstack.org>
Subject:  Re: [openstack-dev] [glance] respecting glance priorities

> Hello Glancers,
>  
> I realize that the weekly priority mailing is a new thing for us, so
> here's a quick reminder of how it works/what it's for.
>  
> Priorities are discussed and set at the weekly meeting and that gives us
> all some focus for what to do in the coming week.
>  
> If you're a glance core: please attend to these items first, before
> reviewing other items or merging other patches.
>  
> If you're not a glance core: priority items are important for the
> project, so a high quality review on them is a good way to get yourself
> noticed as an up-and-coming glance contributor.
>  
> These are called "priorities", not because they're the only things we're
> working on, but because we want to get them completed *first*.
>  
> If you have a patch that didn't make the list, keep in mind that
> OpenStack development is a community effort. If you review other
> people's patches, other people are more likely to review yours.
>  
> (And yes, what prompted this mailing is that I saw some patches merged
> while many of the items below have been languishing for want of
> attention. There are about 18 hours until the weekly Glance meeting, it
> would be nice to see them addressed. :) )
>  
> Here endeth the lesson.
>  
> cheers,
> brian
>  
>  
> On 12/9/16 7:14 AM, Brian Rosmaita wrote:
> > As discussed at the Glance weekly meeting yesterday, the priorities for
> > 12/1 through 12/8, unfortunately look very similar to last week's
> > priorities. Some core reviewers need to step up. The priorities are:
> >
> > Highest priority
> > ================
> >
> > (1) database strategy for rolling upgrades:
> > https://review.openstack.org/#/c/331740/
> > This one has a video to enhance your reviewing pleasure and demonstrate
> > that the approach described actually is workable:
> > https://www.youtube.com/watch?v=Z4iwJRlPqOw
> >
> > (2) glance expand/contract migrations with alembic:
> > https://review.openstack.org/#/c/374278/
> > We need another +2 on this one, preferably from a non-Rackspace person.
> >
> > (3) community images spec update:
> > https://review.openstack.org/#/c/396919/
> > New to the list. The latest patch includes the migration strategy for
> > which Erno said indicated on the patch he'd change his -2 to a +2, so
> > don't let the -2 on the patch stop you from reviewing it.
> >
> > The above three specs need to be reviewed as soon as possible. We are
> > blocking Alex and Hemanth, because the Ocata database migration will
> > handle the community images changes.
> >
> >
> > Really high priority
> > ====================
> > (would be highest if the specs were already approved)
> >
> > (4) Patch to fix a glance_store regression:
> > https://review.openstack.org/#/c/387719/
> > and patch to prevent a related backend misconfiguration:
> > https://review.openstack.org/#/c/388944/
> >
> > (5) Patch to enable better request-id tracking:
> > https://review.openstack.org/#/c/352892/
> > This will be nice for operators, let's get it reviewed and merged!
> >
> > (6) Request for some insights and opinions for bug
> > https://bugs.launchpad.net/glance/+bug/1585917
> >
> >
> > Please take a look
> > ==================
> >
> > (7) glanceclient problem: https://review.openstack.org/#/c/319960/
> >
> > thanks,
> > brian

Also worth noting that for community members with bugs/patches that are a priority to them, the correct place to lobby for that is in the weekly meeting. 

--  
Ian Cordasco
Release CPL/Czar