Hey
The openstack-stable-maint team will be responsible for the stable/grizzly branches of nova, keystone, glance, cinder, quantum, horizon, oslo-incubator and oslo.config.
That team's job is really to evaluate the risk/benefit of a given backported patch and understand the "safe source of fixes for high-impact, user-visible issues" policy documented here:
http://wiki.openstack.org/StableBranch
i.e. we keep an eye out for changes proposed to stable/grizzly and then:
* evaluate risk of a patch * consider how severe the issue is for users * check that it's already fixed on master
Preferably we add a little comment indicating whether a change meets those criteria when adding our +/-2. Also, stable/grizzly reviews need 2 +2s from stable-maint members unless the person proposing the backport is also a stable-maint member.
The question is ... who should be on the team?
Previously, we've included the PTLs and a number of others who are interested in helping out and understand the inclusion criteria.
https://launchpad.net/~openstack-stable-maint/+members#active
The outgoing PTLs are bcwaldon, danwent, heckj and vishy. If any of you guys want to remain on the team, just let me know.
Daviey, zul, eglynn, garyk, ghe.rivero, mapleoin and pixelbeat - if any of you want to bow out, just let me know.
The incoming PTLs are russellb, dolphm, markwash and mark.mcclain. I'll assume all of you want to be added.
Matthias Runge from the Horizon team has also expressed an interest in helping, so I'll add him.
Thanks, Mark.
I'd like to stay on the team
Vish
On Mar 20, 2013, at 1:07 AM, Mark McLoughlin markmc@redhat.com wrote:
Hey
The openstack-stable-maint team will be responsible for the stable/grizzly branches of nova, keystone, glance, cinder, quantum, horizon, oslo-incubator and oslo.config.
That team's job is really to evaluate the risk/benefit of a given backported patch and understand the "safe source of fixes for high-impact, user-visible issues" policy documented here:
http://wiki.openstack.org/StableBranch
i.e. we keep an eye out for changes proposed to stable/grizzly and then:
- evaluate risk of a patch
- consider how severe the issue is for users
- check that it's already fixed on master
Preferably we add a little comment indicating whether a change meets those criteria when adding our +/-2. Also, stable/grizzly reviews need 2 +2s from stable-maint members unless the person proposing the backport is also a stable-maint member.
The question is ... who should be on the team?
Previously, we've included the PTLs and a number of others who are interested in helping out and understand the inclusion criteria.
https://launchpad.net/~openstack-stable-maint/+members#active
The outgoing PTLs are bcwaldon, danwent, heckj and vishy. If any of you guys want to remain on the team, just let me know.
Daviey, zul, eglynn, garyk, ghe.rivero, mapleoin and pixelbeat - if any of you want to bow out, just let me know.
The incoming PTLs are russellb, dolphm, markwash and mark.mcclain. I'll assume all of you want to be added.
Matthias Runge from the Horizon team has also expressed an interest in helping, so I'll add him.
Thanks, Mark.
Openstack-stable-maint mailing list Openstack-stable-maint@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint
On 03/20/2013 05:24 PM, Vishvananda Ishaya wrote:
I'd like to stay on the team
ditto
Vish
On Mar 20, 2013, at 1:07 AM, Mark McLoughlinmarkmc@redhat.com wrote:
Hey
The openstack-stable-maint team will be responsible for the stable/grizzly branches of nova, keystone, glance, cinder, quantum, horizon, oslo-incubator and oslo.config.
That team's job is really to evaluate the risk/benefit of a given backported patch and understand the "safe source of fixes for high-impact, user-visible issues" policy documented here:
http://wiki.openstack.org/StableBranch
i.e. we keep an eye out for changes proposed to stable/grizzly and then:
- evaluate risk of a patch
- consider how severe the issue is for users
- check that it's already fixed on master
Preferably we add a little comment indicating whether a change meets those criteria when adding our +/-2. Also, stable/grizzly reviews need 2 +2s from stable-maint members unless the person proposing the backport is also a stable-maint member.
The question is ... who should be on the team?
Previously, we've included the PTLs and a number of others who are interested in helping out and understand the inclusion criteria.
https://launchpad.net/~openstack-stable-maint/+members#active
The outgoing PTLs are bcwaldon, danwent, heckj and vishy. If any of you guys want to remain on the team, just let me know.
Daviey, zul, eglynn, garyk, ghe.rivero, mapleoin and pixelbeat - if any of you want to bow out, just let me know.
The incoming PTLs are russellb, dolphm, markwash and mark.mcclain. I'll assume all of you want to be added.
Matthias Runge from the Horizon team has also expressed an interest in helping, so I'll add him.
Thanks, Mark.
Openstack-stable-maint mailing list Openstack-stable-maint@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint
Openstack-stable-maint mailing list Openstack-stable-maint@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint
Hey
The openstack-stable-maint team will be responsible for the stable/grizzly branches of nova, keystone, glance, cinder, quantum, horizon, oslo-incubator and oslo.config.
That team's job is really to evaluate the risk/benefit of a given backported patch and understand the "safe source of fixes for high-impact, user-visible issues" policy documented here:
http://wiki.openstack.org/StableBranch
i.e. we keep an eye out for changes proposed to stable/grizzly and then:
- evaluate risk of a patch
- consider how severe the issue is for users
- check that it's already fixed on master
Preferably we add a little comment indicating whether a change meets those criteria when adding our +/-2. Also, stable/grizzly reviews need 2 +2s from stable-maint members unless the person proposing the backport is also a stable-maint member.
The question is ... who should be on the team?
Previously, we've included the PTLs and a number of others who are interested in helping out and understand the inclusion criteria.
https://launchpad.net/~openstack-stable-maint/+members#active
The outgoing PTLs are bcwaldon, danwent, heckj and vishy. If any of you guys want to remain on the team, just let me know.
Daviey, zul, eglynn, garyk, ghe.rivero, mapleoin and pixelbeat - if any of you want to bow out, just let me know.
Count me in please as a continuing member.
The incoming PTLs are russellb, dolphm, markwash and mark.mcclain. I'll assume all of you want to be added.
Just wondering if the two newly-minted Integrated projects will be included in the stable-maint process?
If so, then IMO we should also invite Steve Dake & Julien Danjou on board as the respective incoming PTLs for Heat & Ceilo.
Cheers, Eoghan
Matthias Runge from the Horizon team has also expressed an interest in helping, so I'll add him.
Thanks, Mark.
Openstack-stable-maint mailing list Openstack-stable-maint@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint
On Wed, 2013-03-20 at 11:33 -0400, Eoghan Glynn wrote:
Hey
The openstack-stable-maint team will be responsible for the stable/grizzly branches of nova, keystone, glance, cinder, quantum, horizon, oslo-incubator and oslo.config.
That team's job is really to evaluate the risk/benefit of a given backported patch and understand the "safe source of fixes for high-impact, user-visible issues" policy documented here:
http://wiki.openstack.org/StableBranch
i.e. we keep an eye out for changes proposed to stable/grizzly and then:
- evaluate risk of a patch
- consider how severe the issue is for users
- check that it's already fixed on master
Preferably we add a little comment indicating whether a change meets those criteria when adding our +/-2. Also, stable/grizzly reviews need 2 +2s from stable-maint members unless the person proposing the backport is also a stable-maint member.
The question is ... who should be on the team?
Previously, we've included the PTLs and a number of others who are interested in helping out and understand the inclusion criteria.
https://launchpad.net/~openstack-stable-maint/+members#active
The outgoing PTLs are bcwaldon, danwent, heckj and vishy. If any of you guys want to remain on the team, just let me know.
Daviey, zul, eglynn, garyk, ghe.rivero, mapleoin and pixelbeat - if any of you want to bow out, just let me know.
Count me in please as a continuing member.
Cool.
The incoming PTLs are russellb, dolphm, markwash and mark.mcclain. I'll assume all of you want to be added.
Just wondering if the two newly-minted Integrated projects will be included in the stable-maint process?
If so, then IMO we should also invite Steve Dake & Julien Danjou on board as the respective incoming PTLs for Heat & Ceilo.
No, since they were Integrated in Grizzly. We've typically left it up to projects to manage this for themselves until they are Integrated.
It would be good to talk both projects through the inclusion policy and encourage them to maintain a stable/grizzly branch themselves using a similar policy.
Cheers, Mark.
On Wed, 2013-03-20 at 11:33 -0400, Eoghan Glynn wrote:
Hey
The openstack-stable-maint team will be responsible for the stable/grizzly branches of nova, keystone, glance, cinder, quantum, horizon, oslo-incubator and oslo.config.
That team's job is really to evaluate the risk/benefit of a given backported patch and understand the "safe source of fixes for high-impact, user-visible issues" policy documented here:
http://wiki.openstack.org/StableBranch
i.e. we keep an eye out for changes proposed to stable/grizzly and then:
- evaluate risk of a patch
- consider how severe the issue is for users
- check that it's already fixed on master
Preferably we add a little comment indicating whether a change meets those criteria when adding our +/-2. Also, stable/grizzly reviews need 2 +2s from stable-maint members unless the person proposing the backport is also a stable-maint member.
The question is ... who should be on the team?
Previously, we've included the PTLs and a number of others who are interested in helping out and understand the inclusion criteria.
https://launchpad.net/~openstack-stable-maint/+members#active
The outgoing PTLs are bcwaldon, danwent, heckj and vishy. If any of you guys want to remain on the team, just let me know.
Daviey, zul, eglynn, garyk, ghe.rivero, mapleoin and pixelbeat - if any of you want to bow out, just let me know.
Count me in please as a continuing member.
Cool.
The incoming PTLs are russellb, dolphm, markwash and mark.mcclain. I'll assume all of you want to be added.
Just wondering if the two newly-minted Integrated projects will be included in the stable-maint process?
If so, then IMO we should also invite Steve Dake & Julien Danjou on board as the respective incoming PTLs for Heat & Ceilo.
No, since they were Integrated in Grizzly. We've typically left it up to projects to manage this for themselves until they are Integrated.
It would be good to talk both projects through the inclusion policy and encourage them to maintain a stable/grizzly branch themselves using a similar policy.
Fair enough, I'll add that idea of DIY stable/grizzly maintenance to the agenda for the weekly metering IRC meeting tmrw.
Cheers, Eoghan
2013/3/20 Mark McLoughlin markmc@redhat.com:
Hey
The openstack-stable-maint team will be responsible for the stable/grizzly branches of nova, keystone, glance, cinder, quantum, horizon, oslo-incubator and oslo.config.
That team's job is really to evaluate the risk/benefit of a given backported patch and understand the "safe source of fixes for high-impact, user-visible issues" policy documented here:
http://wiki.openstack.org/StableBranch
i.e. we keep an eye out for changes proposed to stable/grizzly and then:
- evaluate risk of a patch
- consider how severe the issue is for users
- check that it's already fixed on master
Preferably we add a little comment indicating whether a change meets those criteria when adding our +/-2. Also, stable/grizzly reviews need 2 +2s from stable-maint members unless the person proposing the backport is also a stable-maint member.
The question is ... who should be on the team?
Previously, we've included the PTLs and a number of others who are interested in helping out and understand the inclusion criteria.
https://launchpad.net/~openstack-stable-maint/+members#active
The outgoing PTLs are bcwaldon, danwent, heckj and vishy. If any of you guys want to remain on the team, just let me know.
Daviey, zul, eglynn, garyk, ghe.rivero, mapleoin and pixelbeat - if any of you want to bow out, just let me know.
The incoming PTLs are russellb, dolphm, markwash and mark.mcclain. I'll assume all of you want to be added.
Matthias Runge from the Horizon team has also expressed an interest in helping, so I'll add him.
To finish this thread, following changes were performed in openstack-stable-maint group in Gerrit:
* removed bcwaldon, danwent and heckj * added russellb, dolphm, markwash, mark.mcclain and mrunge
I wanted to say thanks to the outgoing members and welcome new ones: I'm looking forward working with you on stable/grizzly !
Cheers, Alan
Thanks Alan -
If I can free up more time in the future, I'll ping y'all and see about helping out going forward in general.
-joe
On Apr 9, 2013, at 3:08 PM, Alan Pevec apevec@gmail.com wrote:
2013/3/20 Mark McLoughlin markmc@redhat.com:
Hey
The openstack-stable-maint team will be responsible for the stable/grizzly branches of nova, keystone, glance, cinder, quantum, horizon, oslo-incubator and oslo.config.
That team's job is really to evaluate the risk/benefit of a given backported patch and understand the "safe source of fixes for high-impact, user-visible issues" policy documented here:
http://wiki.openstack.org/StableBranch
i.e. we keep an eye out for changes proposed to stable/grizzly and then:
- evaluate risk of a patch
- consider how severe the issue is for users
- check that it's already fixed on master
Preferably we add a little comment indicating whether a change meets those criteria when adding our +/-2. Also, stable/grizzly reviews need 2 +2s from stable-maint members unless the person proposing the backport is also a stable-maint member.
The question is ... who should be on the team?
Previously, we've included the PTLs and a number of others who are interested in helping out and understand the inclusion criteria.
https://launchpad.net/~openstack-stable-maint/+members#active
The outgoing PTLs are bcwaldon, danwent, heckj and vishy. If any of you guys want to remain on the team, just let me know.
Daviey, zul, eglynn, garyk, ghe.rivero, mapleoin and pixelbeat - if any of you want to bow out, just let me know.
The incoming PTLs are russellb, dolphm, markwash and mark.mcclain. I'll assume all of you want to be added.
Matthias Runge from the Horizon team has also expressed an interest in helping, so I'll add him.
To finish this thread, following changes were performed in openstack-stable-maint group in Gerrit:
- removed bcwaldon, danwent and heckj
- added russellb, dolphm, markwash, mark.mcclain and mrunge
I wanted to say thanks to the outgoing members and welcome new ones: I'm looking forward working with you on stable/grizzly !
Cheers, Alan
Openstack-stable-maint mailing list Openstack-stable-maint@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint
participants (6)
-
Alan Pevec
-
Eoghan Glynn
-
Gary Kotton
-
heckj
-
Mark McLoughlin
-
Vishvananda Ishaya