Difference between revisions of "Meetings/MuranoAgenda"
< Meetings
(→Agenda) |
(→Agenda) |
||
| Line 6: | Line 6: | ||
=== Agenda === | === Agenda === | ||
| − | * '''Spec review process'''. | + | * '''Spec review process''' (I believe, that we should review specs even if it has -1 from someone). |
* '''Dropping DB downgrades'''. See this ML discussion http://lists.openstack.org/pipermail/openstack-dev/2015-April/061953.html for reasons of dropping db downgrades. And this bug https://bugs.launchpad.net/murano/+bug/1399151 | * '''Dropping DB downgrades'''. See this ML discussion http://lists.openstack.org/pipermail/openstack-dev/2015-April/061953.html for reasons of dropping db downgrades. And this bug https://bugs.launchpad.net/murano/+bug/1399151 | ||
* Possibility of '''Nightly builds''' of stable branches to check gate health. | * Possibility of '''Nightly builds''' of stable branches to check gate health. | ||
Revision as of 21:57, 5 July 2015
We have meetings in #openstack-meeting-alt weekly on Tuesdays at 17:00 UTC.
Next meetings
- July 7, 2015, 17:00 UTC
Agenda
- Spec review process (I believe, that we should review specs even if it has -1 from someone).
- Dropping DB downgrades. See this ML discussion http://lists.openstack.org/pipermail/openstack-dev/2015-April/061953.html for reasons of dropping db downgrades. And this bug https://bugs.launchpad.net/murano/+bug/1399151
- Possibility of Nightly builds of stable branches to check gate health.
- Action Items Review
- Open Discussion
Checklist for the meeting organizer
- Publish the agenda 24h in advance.
- Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action.
- Use http://meetbot.debian.net/Manual.html to get an automatic summary.
- Prepare an outline for the meeting to speed things up.
- Record decisions and commitments; review in the next meeting.
