Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Thierry Carrez wrote: > [...] > I'm mostly away this week at a conference, but now that we have a list > of names, we should set up a meeting early next week to further discuss > team goals and initial leadership. We'll be holding a preliminary meeting today (Monday) at 15:00 UTC in

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

List (not for usage questions) Subject: Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team On 13/11/15 15:10 +0100, Thierry Carrez wrote: >So.. quick summary of this thread so far. > >(-) >* Not enough work to warrant a designated "team&qu

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Matt Riedemann wrote: > [...] > This is basically what I see for PTL of a stable maint team: > > 1. Helping projects deal with stable branch policy and process. We are > decentralizing now but I suspect there will still be a lot of learning > and cat herding needed in individual projects. This

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/13/2015 8:10 AM, Thierry Carrez wrote: So.. quick summary of this thread so far. (-) * Not enough work to warrant a designated "team", now that the work is decentralized and the cats are mostly herding themselves * The change is unlikely to bring a meaningful improvement to the

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 13 November 2015 at 14:10, Thierry Carrez wrote: > So.. quick summary of this thread so far. > > (-) > * Not enough work to warrant a designated "team", now that the work is > decentralized and the cats are mostly herding themselves > * The change is unlikely to bring a

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Excerpts from Thierry Carrez's message of 2015-11-13 15:10:24 +0100: > So.. quick summary of this thread so far. > > (-) > * Not enough work to warrant a designated "team", now that the work is > decentralized and the cats are mostly herding themselves > * The change is unlikely to bring a

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

So.. quick summary of this thread so far. (-) * Not enough work to warrant a designated "team", now that the work is decentralized and the cats are mostly herding themselves * The change is unlikely to bring a meaningful improvement to the situation, or sudden new resources (+) * An empowered

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/11/15 13:39 -0600, Matt Riedemann wrote: On 11/11/2015 8:51 AM, Flavio Percoco wrote: On 09/11/15 21:30 -0600, Matt Riedemann wrote: On 11/9/2015 9:12 PM, Matthew Treinish wrote: On Mon, Nov 09, 2015 at 10:54:43PM +, Kuvaja, Erno wrote: On Mon, Nov 09, 2015 at 05:28:45PM -0500,

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 09/11/15 21:30 -0600, Matt Riedemann wrote: On 11/9/2015 9:12 PM, Matthew Treinish wrote: On Mon, Nov 09, 2015 at 10:54:43PM +, Kuvaja, Erno wrote: On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: On

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/11/2015 8:51 AM, Flavio Percoco wrote: On 09/11/15 21:30 -0600, Matt Riedemann wrote: On 11/9/2015 9:12 PM, Matthew Treinish wrote: On Mon, Nov 09, 2015 at 10:54:43PM +, Kuvaja, Erno wrote: On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: Excerpts from Matt

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/10/2015 5:41 AM, Alan Pevec wrote: The Stable Branch Policy, lets not put it in any repo. Doing that would give indication that we expect changes into it and I'd prefer that policy mostly staying stable as well. What indication did it give when it was in wiki? :) It actually already

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Thierry Carrez wrote: Hi everyone, A few cycles ago we set up the Release Cycle Management team which was a bit of a frankenteam of the things I happened to be leading: release management, stable branch maintenance and vulnerability management. While you could argue

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Tue, Nov 10, 2015 at 10:13:09AM +0100, Thierry Carrez wrote: > Matthew Treinish wrote: > > [...] > > The discussion here is about the cross project effort around stable > > branches, > > which by design is a more limited scope now. Right now the cross project > > effort > > around stable

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Kuvaja, Erno wrote: > [...] > The Stable Branch Policy, lets not put it in any repo. Doing that would give > indication that we expect changes into it and I'd prefer that policy mostly > staying stable as well. It actually already is in a repo:

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

> -Original Message- > From: Matthew Treinish [mailto:mtrein...@kortar.org] > Sent: Tuesday, November 10, 2015 3:12 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [stable] Making stable maintenance its own > Open

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Matthew Treinish wrote: > [...] > The discussion here is about the cross project effort around stable branches, > which by design is a more limited scope now. Right now the cross project > effort > around stable branch policy is really 2 things (both of which ttx already > mentioned): > > 1.

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

>> The Stable Branch Policy, lets not put it in any repo. >> Doing that would give indication that we expect changes into it and I'd >> prefer that policy mostly staying stable as well. What indication did it give when it was in wiki? :) > It actually already is in a repo: >

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Mon, Nov 09, 2015 at 05:41:53PM +0100, Thierry Carrez wrote: > Hi everyone, > > A few cycles ago we set up the Release Cycle Management team which was a > bit of a frankenteam of the things I happened to be leading: release > management, stable branch maintenance and vulnerability management.

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Excerpts from Thierry Carrez's message of 2015-11-09 17:41:53 +0100: > Hi everyone, > > A few cycles ago we set up the Release Cycle Management team which was a > bit of a frankenteam of the things I happened to be leading: release > management, stable branch maintenance and vulnerability

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/9/2015 10:41 AM, Thierry Carrez wrote: Hi everyone, A few cycles ago we set up the Release Cycle Management team which was a bit of a frankenteam of the things I happened to be leading: release management, stable branch maintenance and vulnerability management. While you could argue

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Mon, Nov 09, 2015 at 10:54:43PM +, Kuvaja, Erno wrote: > > On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: > > > Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: > > > > > > > > On 11/9/2015 10:41 AM, Thierry Carrez wrote: > > > > > Hi everyone, > > > > >

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

+1 I think that as OpenStack's customer base grows, this is going to become more and more important, and will get the pain of users not getting updates will increase enough that there *will* be a group of engineers willing to do not only backports and releases, but bugfixes in trunk and gate

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/9/2015 9:12 PM, Matthew Treinish wrote: On Mon, Nov 09, 2015 at 10:54:43PM +, Kuvaja, Erno wrote: On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: On 11/9/2015 10:41 AM, Thierry Carrez wrote: Hi

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Excerpts from Matthew Treinish's message of 2015-11-09 17:09:54 -0500: > On Mon, Nov 09, 2015 at 05:41:53PM +0100, Thierry Carrez wrote: > > Hi everyone, > > > > A few cycles ago we set up the Release Cycle Management team which was a > > bit of a frankenteam of the things I happened to be

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: > > On 11/9/2015 10:41 AM, Thierry Carrez wrote: > > Hi everyone, > > > > A few cycles ago we set up the Release Cycle Management team which was a > > bit of a frankenteam of the things I happened to be leading: release > >

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

> -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: 09 November 2015 16:42 > To: OpenStack Development Mailing List > Subject: [openstack-dev] [stable] Making stable maintenance its own > OpenStack project team > > Hi everyone, > > A few cycles ago we set

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

> -Original Message- > From: Matthew Treinish [mailto:mtrein...@kortar.org] > Sent: 09 November 2015 22:40 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [stable] Making stable maintenance its own > OpenStack project tea

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: > Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: > > > > On 11/9/2015 10:41 AM, Thierry Carrez wrote: > > > Hi everyone, > > > > > > A few cycles ago we set up the Release Cycle Management team which was a > > >