Difference between revisions of "Meetings/StableTeam"
< Meetings
(→Agenda) |
(→Agenda) |
||
| Line 36: | Line 36: | ||
* Release News | * Release News | ||
** Check for stable/liberty point release candidates as we wind down to m-3: http://lists.openstack.org/pipermail/openstack-dev/2016-February/086362.html | ** Check for stable/liberty point release candidates as we wind down to m-3: http://lists.openstack.org/pipermail/openstack-dev/2016-February/086362.html | ||
| + | |||
| + | * 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. | ||
| + | *** Note that the stable:follows-policy tag may be used to determine when projects stable branches go end of life (EOL). | ||
* Stuck Reviews - discuss controversial backports | * Stuck Reviews - discuss controversial backports | ||
Revision as of 15:59, 7 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
- Monday February 29th at 2100 UTC in #openstack-meeting-4 (mriedem to chair)
- Tuesday March 8th 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.
- 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)
- tonyb to talk to lifeless about fixtures bug https://bugs.launchpad.net/python-fixtures/+bug/1542984
- Ihar capped testtools<2.0.0 in g-r on stable/kilo: https://review.openstack.org/#/c/276275/ but things are still failing: https://review.openstack.org/#/c/273274/
- bknudson to propose dropping upper-constraints from stable/kilo to see if the reqs job will work without it
- Result: it didn't work but we didn't need it anyway; ksm test-requirements-py3.txt was manually updated on stable/kilo to get Jenkins passing, so most likely there is a bug in the g-r sync bot since it's not updating the *requirements-py3.txt files.
- tonyb to talk to lifeless about fixtures bug https://bugs.launchpad.net/python-fixtures/+bug/1542984
- Release News
- Check for stable/liberty point release candidates as we wind down to m-3: http://lists.openstack.org/pipermail/openstack-dev/2016-February/086362.html
- 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.
- Note that the stable:follows-policy tag may be used to determine when projects stable branches go end of life (EOL).
- (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/ - dependent on the follow-stable-policy tag
- script to check for backport-potential bugs which are fixed on trunk but backports are not yet proposed
- Open discussion
- (mriedem): Do we want/need a summit session? I figure there will at least be some overlap with the release and QA teams on how long to keep stable/liberty.
