Difference between revisions of "Meetings/StableTeam"
< Meetings
(→Agenda) |
(→Next Meeting) |
||
Line 16: | Line 16: | ||
=== Next Meeting === | === Next Meeting === | ||
− | |||
* Tuesday March 22nd at 1500 UTC in #openstack-meeting-3 (mriedem to chair) | * 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 === | === Agenda === |
Revision as of 02:10, 18 March 2016
Contents
Weekly OpenStack Stable Team Meeting
This is a weekly meeting to discuss OpenStack stable branches.
- Wiki: https://wiki.openstack.org/wiki/StableBranch
- Project team guide: http://docs.openstack.org/project-team-guide/stable-branches.html
- Issues tracker: https://etherpad.openstack.org/p/stable-tracker
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.
- Status (do not remove)
- periodic-stable job faliures (logstash): http://goo.gl/5qiw2U
- openstack-health dashboard: http://status.openstack.org/openstack-health/#/g/build_queue/periodic-stable
- known issues: https://etherpad.openstack.org/p/stable-tracker
- Action items from previous meeting (do not remove)
- mriedem to check which projects haven't done a stable/liberty release since m-1
- Not done, I'm a failure! Really need to get https://review.openstack.org/#/c/270273/ cleaned up to automate this.
- mriedem to check which projects haven't done a stable/liberty release since m-1
- 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?
- (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.
- Tagging
- (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.
- https://review.openstack.org/#/q/%22stable:follows-policy%22
- (mriedem): The stable:follows-policy tag is official: http://governance.openstack.org/reference/tags/stable_follows-policy.html
- 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).
- 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