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 ping lifeless about fixtures bug https://bugs.launchpad.net/python-fixtures/+bug/1542984
+
** mriedem to check which projects haven't done a stable/liberty release since m-1
−
*** Done: the bug is fixed, fixtures .1.2.1 is out.
+
*** Not done, I'm a failure! Really need to get https://review.openstack.org/#/c/270273/ cleaned up to automate this.
−
** tonyb to push up his initial script for scraping backport potential bugs
 
−
*** ?
 
−
** mriedem to talk to dhellmann about cross-project discussion for stable/liberty timeline
 
−
*** Done; see discussion with fungi: http://eavesdrop.openstack.org/irclogs/%23openstack-stable/%23openstack-stable.2016-03-07.log.html#t2016-03-07T18:54:05
 
−
*** We'll have a fishbowl session at the summit to talk about stable branch EOL policy, focusing on Kilo.
 
  
 
* 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.
 
** (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.
 +
*** 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
 
** (mriedem): The stable:follows-policy tag is official: http://governance.openstack.org/reference/tags/stable_follows-policy.html
 
*** Projects need to start proposing patches to the governance repo to apply that tag to their project.
 
*** Projects need to start proposing patches to the governance repo to apply that tag to their project.
−
*** Note that the stable:follows-policy tag may be used to determine when projects stable branches go end of life (EOL).
+
*** https://review.openstack.org/#/q/%22stable:follows-policy%22
  
 
* Stuck Reviews - discuss controversial backports
 
* Stuck Reviews - discuss controversial backports
Line 49: Line 45:
  
 
* 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/ - dependent on the follow-stable-policy tag
+
** script to check for unreleased changes, dhellmann has a WIP here: https://review.openstack.org/#/c/270273/
 
** script to check for backport-potential bugs which are fixed on trunk but backports are not yet proposed
 
** script to check for backport-potential bugs which are fixed on trunk but backports are not yet proposed
 +
** 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
−
** ?
+
** 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
  
 
=== Previous Meetings ===
 
=== Previous Meetings ===

Revision as of 19:07, 14 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

  • Monday March 14th at 2100 UTC in #openstack-meeting-4 (mriedem to chair)
  • Tuesday March 22nd at 1500 UTC in #openstack-meeting-3 (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)
  • 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.
      • 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?
  • Stuck Reviews - discuss controversial backports
    •  ?
  • 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 backport-potential bugs which are fixed on trunk but backports are not yet proposed
    • 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).

Previous Meetings

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

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/StableTeam&oldid=122198"