Jump to: navigation, search

Difference between revisions of "Meetings/StableTeam"

(Next Meeting)
(Agenda)
Line 29: Line 29:
  
 
* Action items from previous meeting (do not remove)
 
* Action items from previous meeting (do not remove)
** mriedem to check which projects haven't done a stable/liberty release since m-1
+
** mriedem to talk to Daviey, ttx and dhellmann about a stable/kilo release
*** Not done, I'm a failure! Really need to get https://review.openstack.org/#/c/270273/ cleaned up to automate this.
+
*** The next kilo release is scheduled for 2016-05-02 (which is also the scheduled EOL date). Kilo is still a coordinated release and historically CVEs have not triggered those releases so we'll wait until 2016-05-02. Note that we'll still be talking at the summit about extending stable/kilo another 6 months, but we might have to consider EOL for some projects that aren't passing Jenkins anymore, e.g. Ironic: https://review.openstack.org/#/c/271391/
 +
** mriedem to start prodding other projects like keystone and cinder to apply for the stable:follows-policy tag
 +
*** cinder and keystone were poked last week, so far no governance changes for the stable:follows-policy tag on those projects.
  
 
* Release News
 
* Release News
** (mriedem) Nova and Ceilometer need to do a stable/kilo release (Nova has a CVE fix and Ceilometer released a regression). Does Daviey organize a mass stable/kilo release or should we just release those two projects? Note we plan on talking about Kilo EOL dates at the summit.
+
** designate 1.0.2 release request for liberty: https://review.openstack.org/295527
*** In the before-times we released en masse on pre-scheduled dates. Should we still do that even though we know we have CVE and breaking fixes?
 
  
 
* Tagging
 
* Tagging
** (mriedem): The stable:follows-policy tag is official: http://governance.openstack.org/reference/tags/stable_follows-policy.html
+
** designate: https://review.openstack.org/#/c/289513/
*** Projects need to start proposing patches to the governance repo to apply that tag to their project.
+
** neutron + friends: https://review.openstack.org/289970
*** https://review.openstack.org/#/q/%22stable:follows-policy%22
+
** oslo: https://review.openstack.org/292633
 +
** trove: https://review.openstack.org/#/c/295733/
  
 
* Stuck Reviews - discuss controversial backports
 
* Stuck Reviews - discuss controversial backports
Line 45: Line 47:
  
 
* Tooling (skip, nothing new)
 
* Tooling (skip, nothing new)
** script to check for unreleased changes, dhellmann has a WIP here: https://review.openstack.org/#/c/270273/
+
** script to check for unreleased changes https://review.openstack.org/#/c/270273/ is merged; zuul cloner dumps a lot of info logging and it would be nice to disable that...
** script to check for backport-potential bugs which are fixed on trunk but backports are not yet proposed
+
** TODO: script to check for backport-potential bugs which are fixed on trunk but backports are not yet proposed; markus_z might have something for this in nova.
** reviewstats; there is a 'stable' group but it's only for stable-maint-core, there isn't an easy way (that I can see) to check for stable branch reviewers on a given project (would have to add it).
+
** TODO: reviewstats; there is a 'stable' group but it's only for stable-maint-core, there isn't an easy way (that I can see) to check for stable branch reviewers on a given project (would have to add it).
  
 
* Open discussion
 
* Open discussion
** (mriedem) FYI, etherpad on stable branch EOL policy discussion for summit (please don't hack this up yet): https://etherpad.openstack.org/p/stable-branch-eol-policy-newton
+
** ?
** (mriedem) PTL intentions: http://lists.openstack.org/pipermail/openstack-dev/2016-March/089289.html
 
  
 
=== Previous Meetings ===
 
=== Previous Meetings ===

Revision as of 14:27, 22 March 2016

Weekly OpenStack Stable Team Meeting

This is a weekly meeting to discuss OpenStack stable branches.

Meetings

  • Meeting Times and IRC Channels: http://eavesdrop.openstack.org/#Stable_Team_Meeting
    • Every two weeks (on odd weeks) on Monday at 2100 UTC in #openstack-meeting-4 (IRC webclient)
    • Every two weeks (on even weeks) on Tuesday at 1500 UTC in #openstack-meeting-3 (IRC webclient)
  • Chaired by: Matt Riedemann <mriedem@us.ibm.com> (irc: mriedem)

Next Meeting

  • Tuesday March 22nd at 1500 UTC in #openstack-meeting-3 (mriedem to chair)
  • Monday March 28th at 2100 UTC in #openstack-meeting-4 (mriedem to chair)

Agenda

Please feel free to add items to the Agenda but prefix with your IRC nickname.

  • Action items from previous meeting (do not remove)
    • mriedem to talk to Daviey, ttx and dhellmann about a stable/kilo release
      • The next kilo release is scheduled for 2016-05-02 (which is also the scheduled EOL date). Kilo is still a coordinated release and historically CVEs have not triggered those releases so we'll wait until 2016-05-02. Note that we'll still be talking at the summit about extending stable/kilo another 6 months, but we might have to consider EOL for some projects that aren't passing Jenkins anymore, e.g. Ironic: https://review.openstack.org/#/c/271391/
    • mriedem to start prodding other projects like keystone and cinder to apply for the stable:follows-policy tag
      • cinder and keystone were poked last week, so far no governance changes for the stable:follows-policy tag on those projects.
  • Stuck Reviews - discuss controversial backports
    •  ?
  • Tooling (skip, nothing new)
    • script to check for unreleased changes https://review.openstack.org/#/c/270273/ is merged; zuul cloner dumps a lot of info logging and it would be nice to disable that...
    • TODO: script to check for backport-potential bugs which are fixed on trunk but backports are not yet proposed; markus_z might have something for this in nova.
    • TODO: reviewstats; there is a 'stable' group but it's only for stable-maint-core, there isn't an easy way (that I can see) to check for stable branch reviewers on a given project (would have to add it).
  • Open discussion
    •  ?

Previous Meetings

http://eavesdrop.openstack.org/meetings/stable/