Jump to: navigation, search

Difference between revisions of "Meetings/MuranoAgenda"

(Agenda)
(Agenda)
Line 12: Line 12:
 
#link https://wiki.openstack.org/wiki/Juno_Release_Schedule
 
#link https://wiki.openstack.org/wiki/Juno_Release_Schedule
 
* [ruhe] https://blueprints.launchpad.net/murano/+spec/engine-test-based-on-murano-pythonclient
 
* [ruhe] https://blueprints.launchpad.net/murano/+spec/engine-test-based-on-murano-pythonclient
i suggest to defer merge of this BP util we make sure that murano-ci is stable enough - at least two weeks without false negatives
+
i suggest to defer merge of this BP until we make sure that murano-ci is stable enough - at least two weeks without false negatives
 
* TBD (launchpad is down atm)
 
* TBD (launchpad is down atm)
  

Revision as of 15:23, 5 August 2014

We have meetings in #openstack-meeting-alt weekly on Tuesdays at 17:00 UTC.

Next meetings

  • July 29, 2014, 17:00 UTC (chaired by katyafervent)

Agenda

  • Action Items Review

katyafervent Extend the description of https://blueprints.launchpad.net/murano/+spec/murano-api-exception-handling

  • Juno-3 and release schedule
  1. link https://launchpad.net/murano/+milestone/juno-3
  2. link https://wiki.openstack.org/wiki/Juno_Release_Schedule

i suggest to defer merge of this BP until we make sure that murano-ci is stable enough - at least two weeks without false negatives

  • TBD (launchpad is down atm)

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.

Previous meetings

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