Success Bot Says
- kong: Qinling now supports Node.js runtime(experimental)
- AJaeger: Jenkins user and jenkins directory on images are gone. /usr/local/jenkins is only created for legacy jobs
- eumel8: Zanata 4 is now here [0]
- smcginnis: Queens has been released!!
- kong: welcome openstackstatus to #openstack-qinling channel!
- Tell us yours in OpenStack IRC channels using the command “#success <comment>”
Thanks Bot Says
- Thanks dhellmann for setting up community wide goals + good use of storyboard [0]
- Thanks ianw for kind help on upgrading to Zanata 4 which has much better UI and improved APIs!
- Tell us yours in OpenStack IRC channels using the command “#thanks <comment>”
Community Summaries
- Release countdown [0]
- TC report [1]
- Technical Committee status update [2]
PTG Summaries
Here’s some summaries that people wrote for their project at the PTG:
- Documentation and i18n [0]
- First Contact SIG [1]
- Cinder [2]
- Mistral [3]
- Interop [4]
- QA [5]
- Release cycle versus downstream consuming models [6]
- Nova Placements [7]
- Kolla [8]
- Oslo [9]
- Ironic [10]
- Cyborg [11]
OpenStack Queens is Officially Released!
Congratulations to all the teams who contributed to this release! Release notes of different projects for Queens are available [0] and a list of projects [1] that still need to approve their release note patches!
Release Cycles vs. Downstream consumers PTG Summary
Notes can be found on the original etherpad [0]. A TC resolution is in review [1]
TLDR summary:
- No consensus on longer / shorter release cycles
- Focus on FFU to make upgrades less painful
- Longer stable branch maintenance time (18 months for Ocata)
- Bootstrap the “extended maintenance” concept with common policy
- Group most impacted by release cadence are packagers/distros/vendors
- Need for finer user survey questions on upgrade models
- Need more data and more discussion, next discussion at Vancouver forum
- Release Management team tracks it between events
Pros and Cons of face-to-face Meetings
Some contributors might not be able to attend the PTG for various reasons:
- Health issues
- Privilege issues (like not getting visa or travel permits)
- Caretaking responsibilities (children, other family, animals, plants)
- Environmental concerns
There is a concern if this is preventing us from meeting our four opens [1] if people are not able to attend the events.
The PTG sessions are not recorded, but there is a super user article on how teams can do this themselves [0]. At the PTG in Denver, the OpenStack Foundation provided bluetooth speakers for teams to help with remote participation.
Consensus is this may not be trivial for everyone and it could still be a challenge for remote participants due to things like audio quality. Some people at the PTG in Dublin due to the weather had to participate remotely from their hotel room and felt it challenging to partipate.
Leave a Reply