da Agency

Developer Mailing List Digest February 17-23rd

Helpful PTG links

PTG is around the corner. Here are some helpful links:

Main welcome email http://lists.openstack.org/pipermail/openstack-dev/2018-February/127611.html
Quick links: http://ptg.openstack.org/
PDF schedule: http://lists.openstack.org/pipermail/openstack-dev/attachments/20180221/5c279bb3/attachment-0002.pdf
PDf map for PTG venue: http://lists.openstack.org/pipermail/openstack-dev/attachments/20180221/5c279bb3/attachment-0003.pdf

Success Bot Says

mhayden got centos OSA gate under 2h today
thingee: we have an on-boarding page and documentation for new contributors! [0]
Tell us yours in OpenStack IRC channels using the command “#success <comment>”
More: https://wiki.openstack.org/wiki/Successes

[0] – https://www.openstack.org/community

Thanks Bot Says

Thanks pkovar for keep the Documentation team going!
Thanks pabelanger and infra for getting ubuntu mirrors repaired and backup quickly!
Thanks lbragstad for helping troubleshoot an intermittent fernet token validation failure in puppet gates
Thanks TheJulia for helping me with a problem last week, it was really a networking problem issue, like you said so
Thanks tosky for backporting devstack ansible changes to pike!
Thanks thingee for Thanks Bot
Thanks openstackstatus for logging our things
Thanks strigazi for the v1.9.3 image
Thanks smcginnis for not stopping this.
Tell us yours in OpenStack IRC channels using the command “#thanks <comment>”
More: https://wiki.openstack.org/wiki/Thanks

Community Summaries

TC report [0]
POST /api-sig/news [1]
Release countdown [2]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127584.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127651.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127465.html

Vancouver Community Contributor Awards

The Community contributor awards gives recognition to those that are undervalued, don’t know they’re appreciated, bind the community together, keep things fun, or challenge some norm. There are a lot of people out there that could use a pat on the back and affirmation that they do good work in the community.

Nomination period is open now [0] until May 14th. Winners will be announced in feedback session at Vancouver.

[0] – https://openstackfoundation.formstack.com/forms/cca_nominations_vancouver

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127634.html

Release Naming For S – time to suggest a name!

It’s time to pick a name for our “S” release! Since the associated Summit will be in Berlin, the Geographic location has been chosen as “Berlin” (state). Nominations are now open [0]. Rules and processes can be seen on the Governance site [1].

[0] – https://wiki.openstack.org/wiki/Release_Naming/S_Proposals
[1] – https://governance.openstack.org/tc/reference/release-naming.html

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127592.html

Final Queens RC Deadline

Thursday 22nd of April is the deadline for any final Queens release candidates. We’ll enter a quiet period for a week in preparation of tagging the final Queens release during the PTG week. Make sure if  you have patches merged to stable/queens that you propose a new RC before the deadline. PTLs should watch for a patch from the release management team tagging the final release. While not required, an acknowledgement on the patch would be appreciated.

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127540.html

Do Not Import oslo_db.tests.*

Deprecations were made on oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase. In a patch [0], and assumption was made to that these should be imported from oslo_db.tests.sqlalchemy. Cinder, Ironic and Glance have been found with this issue [1].

Unfortunately these were not prefixed with underscores to comply with naming conventions for people to recognize private code. The tests module was included for consumers to run those tests on their own packages easily.

[0] – https://review.openstack.org/#/c/522290/
[1] – http://codesearch.openstack.org/?q=oslo_db.tests&i=nope&files=&repos=

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2018-February/thread.html#127531

Some New Zuul Features

Default timeout is 30 minutes for “post-run” phase of the job. A new attribute “timeout” [0] can set this to something else, which could be useful for a job that performs a long artifact upload.

Two new job attributes added “host-vars” and “group-vars” [1] which behave like “vars” but applies to a specific host or group.

[0] – https://docs.openstack.org/infra/zuul/user/config.html#attr-job.post-timeout
[1] – https://docs.openstack.org/infra/zuul/user/config.html#attr-job.host-vars

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127591.html
Quelle: openstack.org

da Agency

OpenStack turns 8: Welcoming new users, more collaboration and new projects

We are celebrating the 8th birthday of OpenStack with the entire OpenStack community during July! OpenStack is an integration engine for diverse technologies, fostering collaboration among emerging communities, and the Foundation facilitates the development of many innovative projects in the open infrastructure space. None of it would be possible without the quickly growing, global community. There are now more than 90,000 community members across 183 countries and more than 670 supporting companies. We think that deserves a worldwide celebration!

 
We’ve invited all our user groups to celebrate with us. This month, more than 30 OpenStack birthday parties will be thrown all over the world – celebrating the OpenStack community!  We encourage everyone to find a birthday party in your area and join your fellow community members to toast each other on another great year! Don’t forget to post and share your pictures and memories on Flickr.
 
Find a local celebration in your area:
Paris, France – June 25
Vietnam – July 1
Los Angeles – July 8
Portland, Oregon – July 9
San Francisco, California – July 10
Sweden – July 12
Virginia – July 12
Moscow, Russia – July 13
Rennes, France – July 16
San Diego, California – July 17
Greece – July 18
Tunisia – July 18
Barcelona – July 19
Mexico City – July 19
Nigeria – July 19
Philippines – July 20
Colorado, USA – July 24
Thailand – July 24
Bucharest, Romania – July 25
Ghana – July 25
Brazil – July 27
Korea – July 27
Durban – July 28
Guatemala – July 30
Iran – July 31
Japan – August 2
Seattle, Washington – August 8
Cote d’Ivoire – August 25
Quelle: openstack.org

da Agency

OpenStack swag voting: Round 2

Thanks for voting on your favorite OpenStack swag designs yesterday! See the second set of designs below, then head over to Twitter to vote on this round.
Check Twitter on Monday to see the winning designs!
 
We Are OpenStack:

OpenStack Worldwide:

Stacker Burst:

Fight for the Users:

Quelle: openstack.org

da Agency

Vote for your favorite OpenStack swag!

The OSF Swag Store is coming soon, but first, we need your help!
Which of the below designs is your favorite? Tell us know in our Twitter poll and check back tomorrow for another round.
OpenStack Logo:

I <3 OpenStack:

Playing for an Open World:

Free as in Beer, Speech, & Love:

 
Quelle: openstack.org

da Agency

User Group Newsletter – January 2018

Welcome to 2018!
 
Important Vancouver Summit Updates
The countdown is on until the next Summit in May. Below are some important updates regarding CFP, Travel and Summit Passes

CFP is now open!

Call for presentations are now open for the Vancouver Summit. The deadline to submit your proposal is February 8th.
There are some new changes to the structure of the CFP, such as track organisation. Read more here. 

Summit Passes and Hotels

These sold quick in 2015 when we last went to Vancouver, don’t miss out and secure yours today. You can do so here. 

Visas

For information regarding Visa applications and invitation letters, read about it here.
As a general planning guideline, if a visa is needed, a foreign traveler should apply for his or her visa as soon as possible, preferably no later than 60 days before the travel date.

Travel Support Program

The Travel Support Program (TSP) aims to facilitate participation of key contributors to the OpenStack Summit by covering the costs for their travel and accommodations. The grants will cover a combination of flights, accommodation, and access pass to the Summit. More details here.
All contributors to OpenStack (developers, documentation writers, organizers of user groups around the world, Ask moderators, speakers, translators, etc) are invited to submit a request. You can apply by filling out this form.

More questions?

Got any other questions about the Summit? There is an excellent FAQ here. 

Ops Meetup Tokyo
The next OpenStack Ops Meetup is happening March 6-7 in Tokyo.
Register here.
Information from Wiki
Project Teams Gathering (PTG)
The Project Teams Gathering (PTG) in Dublin February 26 – March 2. It’s an event for anyone who self-identifies as a member in a specific given project team as well as operators who are specialists on a given project and willing to spend their time giving feedback on their use case and contributing their usage experience to the project team.
Upcoming Industry Events
FODSEM
The Foundation will be present at FODSEM in Brussels, February 3-4 2018.
OpenStack booth will be in building K, level 1

https://fosdem.org/2018

OpenStack delivers a keynote at Chaosscon
Feb 2, 2018 in Brussels

http://grimoirelab.github.io/con/

Upcoming CFP
LF Open Source Leadership
Closing date: January 21, 2018
OSCON 2018
Closing Date: January 30, 2018
LinuxCon ContainerCon | CloudOpen China
Closing Date: March 4, 2018
ONS Europe
Closing Date: June 24, 2018
OpenStack Technical Committee E-office Hours
The TC has e-office hours each week to field any questions you may have.
Find out more details here:

https://governance.openstack.org/tc/

Quelle: openstack.org

da Agency

Developer Mailing List Digest January 5-12th

Success Bot Says

e0ne on #openstack-horizon [0]: amotoki runs horizon with django 2.0

tristianC on #rdo [1]: review.rdoproject.org is now running sf-2.7

mriedem on #openstack-nova [2]: nova merged alternate hosts support for server build

mriedem on #openstack-nova [3]: After a week of problems, finally got a volume multiattach test run to actually attach a volume to two instances without melting the world. o/

zaneb [4]: 14% reduction in Heat memory use in the TripleO gate from fixing https://bugs.launchpad.net/heat/+bug/1731349

Tell us yours in OpenStack IRC channels using the command “#success <comment>”

More: https://wiki.openstack.org/wiki/Successes

[0] – http://eavesdrop.openstack.org/irclogs/%23openstack-horizon/%23openstack-horizon.2017-12-18.log.html
[1] – http://eavesdrop.openstack.org/irclogs/%23rdo/%23rdo.2017-12-21.log.html
[2] – http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2017-12-22.log.html
[3] – http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-01-05.log.html
[4] – http://eavesdrop.openstack.org/irclogs/%23tripleo/%23tripleo.2018-01-09.log.html

Community Summaries

Technical Committee Status update [0]

POST /api-sig/news [1]

Release countdown [2]

Nova placement resource provider update [3]

Keystone team update [4]

Nova Notification Update [5]

TC report [6]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2018-January/126178.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2018-January/126147.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2018-January/125996.html
[3] – http://lists.openstack.org/pipermail/openstack-dev/2018-January/126179.html
[4] – http://lists.openstack.org/pipermail/openstack-dev/2018-January/126188.html
[5] – http://lists.openstack.org/pipermail/openstack-dev/2018-January/126025.html
[6] – http://lists.openstack.org/pipermail/openstack-dev/2018-January/126082.html

Community Goals for Rocky

So far one goal has been proposed by Kendall Nelson for migrating to Storyboard. It was agreed to postpone the goal until the S cycle, as it could take longer than six months to achieve. There is a good backlog of goals [0], just no champions. It’ll be bad for momentum if we have a cycle with no community wide goal.

[0] – https://etherpad.openstack.org/p/community-goals

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2018-January/126090.html

PTG Post-lunch Presentations

Feedback received from past PTG session(s) was the lack of situational awareness and missed opportunity for “global” communication at the event. In Dublin we’d used the end of the lunch break to for communications that could be interesting to OpenStack upstream developers and project team members. The idea is not to find a presentation for everyday, but if we find content that is generally useful. Interesting topics include general guidance to make the most of the PTG weeks (good Monday content), development tricks, code review etiquette, new library features you should adopt, lightning talks (good Friday content). We’d like to keep the slot under 20 minutes. If you have ideas please fill out this etherpad [0] in a few weeks.

[0] – https://etherpad.openstack.org/p/dublin-PTG-postlunch

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2018-January/126102.html
Quelle: openstack.org

da Agency

Developer Mailing List Digest November 11-17

Summaries

POST /api-sig/news [0]
Release countdown for week R-14, November 18-24 [1]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124633.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124631.html
 
Upstream Long Term Support Releases
The Sydney Summit had a very well attended and productive session [0] about to go about keeping a selection of past releases available and maintained for long term support (LTS).
In the past the community has asked for people who are interested in old branches being maintained for a long time to join the Stable Maintenance team with the premise that if the stable team grew, it could support more branches for longer periods. This has been repeated for about years and is not working.
This discussion is about allowing collaboration on patches beyond end of life (EOL) and enable whoever steps up to maintain longer lived branches to come up with a set of tests that actually match their needs with tests that would be less likely to bitrot due to changing OS/PYPI substrate. We need to lower expectations of what we’re likely to produce will get more brittle the older the branch gets. Any burden created by taking on more work is absorbed by people doing the work, as does not unduly impact the folks not interested in doing the work.
The idea is to continue the current stable policy more or less as it is. Development teams take responsibility of a couple of stable branches. At some point what we now call an EOL branch, instead of deleting it we would leave it open and establish a new team of people who want to continue to main that branch. It’s anticipated the members of those new teams are coming mostly from users and distributors. Not all branches are going to attract teams to maintain them, and that’s OK.
We will stop tagging these branches so the level of support they provide are understood. Backports and other fixes can be shared, but to consume them, a user will have to build their own packages.
Test jobs will run as they are, and the team that maintain the branch could decide how to deal with them. Fixing the jobs upstream where possible is preferred, but depending on who is maintaining the branch, the level of support they are actually providing and the nature of the breakage, removing individual tests or whole jobs is another option. Using third-party testing came up but is not required.
Policies for the new team being formed to maintain these older branches is being discussed in an etherpad [2].
Some feedback in the room expressed they to start one release a year who’s branch isn’t deleted after a year. Do one release a year and still keep N-2 stable releases around. We still do backports to all open stable branches. Basically do what we’re doing now, but once a year.
Discussion on this suggestion extended to the OpenStack SIG mailing list [1] suggesting that skip-release upgrades are a much better way to deal with upgrade pain than extending cycles. Releasing every year instead of a 6 months means our releases will contain more changes, and the upgrade could become more painful. We should be release often as we can and makes the upgrades less painful so versions can be skipped.
We have so far been able to find people to maintain stable branches for 12-18 months. Keep N-2 branches for annual releases open would mean extending that support period to 2+ years. If we’re going to do that, we need to address how we are going to retain contributors.
When you don’t release often enough, the pressure to get a patch “in” increases. Missing the boat and waiting for another year is not bearable.
[0] – https://etherpad.openstack.org/p/SYD-forum-upstream-lts-releases
[1] – http://lists.openstack.org/pipermail/openstack-sigs/2017-November/000149.html
[2] – https://etherpad.openstack.org/p/LTS-proposal
Quelle: openstack.org

da Agency

Developer Mailing List Digest November 18-27

Community Summaries

Glance priorities [0]
Nova placement resource provider update [1]
Keystone Upcoming Deadlines [2]
Ironic priorities and subteam reports [3]
Keystone office hours [4]
Nova notification update [5]
Release countdown [6]
Technical committee status update [7]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124678.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124429.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124727.html
[3] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124731.html
[4] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124820.html
[5] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124900.html
[6] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124882.html
[7] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124875.html

Self-healing SIG created

Adam Spiers announced the formation of a SIG around self-healing. Its scope is to coordinate the use and development of several OpenStack projects which can be combined in various ways to manage OpenStack infrastructure in a policy-driven fashion, reacting to failures and other events by automatically healing and optimising services.

Full thread: http://lists.openstack.org/pipermail/openstack-sigs/2017-November/000170.html

Proposal for a QA SIG

A proposal to to have a co-existing QA special interest group (SIG) that would be a place for downstream efforts to have a common place in collaborating and sharing tests. Example today the OPNFV performs QA on OpenStack releases today and are actively looking for opportunities to share tools and test cases. While a SIG can exist to do some code, the QA team will remain for now since there are around 15 QA projects existing like Tempest and Grenade.

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-November/thread.html#124662

Improving the Process for Release Marketing

Collecting and summarizing “top features” during release time is difficult for both PTL’s and Foundation marketing. A system is now in place for PTL’s to highlight release notes [0]. Foundation marketing will work with the various teams if needed to understand and make things more press friendly.

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-November/thread.html#124726

[0] – http://git.openstack.org/cgit/openstack/releases/tree/README.rst#n466
Quelle: openstack.org

da Agency

Developer Mailing List Digest November 25 to December 1st

News

Project Team Gather (PTG) in Dublin registration is live [0]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124978.html

Community Summaries

TC report by Chris Dent [0]

Release countdown [1]

Technical Committee Status updated [2]

POST /api-sig/news [3]

Nova notification update [4]

Nova placement resource providers update [5]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124964.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/125054.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2017-December/125099.html
[3] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/125071.html
[4] – http://lists.openstack.org/pipermail/openstack-dev/2017-December/125146.html
[5] – http://lists.openstack.org/pipermail/openstack-dev/2017-December/125117.html

Dublin PTG Format

We will continue themes as we did in Denver (Monday-Tuesday), but shorter times like half days. Flexibility is added for other groups to book the remaining available rooms in 90-min slots on-demand driven by the PTG Bot (Wednesday-Friday.

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-November/thread.html#124898

First Contact SIG

A wiki has been created for the group [0]. The group is looking for intersted people being points of contact for newcomers and what specified time zones. Resource links like contributor portal, mentoring wiki, Upstream Institute, outreachy are being collected on the wiki page. A representative from the operators side to chair and represent would be good.

[0] – https://wiki.openstack.org/wiki/First_Contact_SIG

Policy Goal Queens-2 Update

Queens-2 coming to a close, we recap our community wide goal for policies [0]. If you want your status changed, contact Lance Bragstad. Use the topic policy-and-docs-in-code for tracking related code changes.

Not Started

openstack/ceilometer

openstack/congress

openstack/networking-bgpvpn

openstack/networking-midonet

openstack/networking-odl

openstack/neutron-dynamic-routing

openstack/neutron-fwaas

openstack/neutron-lib

openstack/solum

openstack/swift

In Progress

openstack/barbican

openstack/cinder

openstack/cloudkitty

openstack/glance

openstack/heat

openstack/manila

openstack/mistral

openstack/neutron

openstack/panko

openstack/python-heatclient

openstack/tacker

openstack/tricircle

openstack/trove

openstack/vitrage

openstack/watcher

openstack/zaqar

Completed

openstack/designate

openstack/freezer

openstack/ironic

openstack/keystone

openstack/magnum

openstack/murano

openstack/nova

openstack/octavia

openstack/sahara

openstack/searchlight

openstack/senlin

openstack/zun

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-November/thread.html#124966

Tempest Plugin Split Goal

A list of open reviews [0] is available for the Tempest plugin split goal [1].

Not Started

Congress
ec2-api
freezer
mistral
monasca
senlin
tacker
Telemetry
Trove
Vitrage

In Progress

Cinder
Heat
Ironic
magnum
manila
Neutron
murano
networking-l2gw
octavia

Completed

Barbican
CloudKitty
Designate
Horizon
Keystone
Kuryr
Sahara
Solum
Tripleo
Watcher
Winstackers
Zaqar
Zun

[0] – https://review.openstack.org/#/q/topic:goal-split-tempest-plugins+status:open
[1] – https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html
Quelle: openstack.org

da Agency

Developer Mailing List Digest December 9-15th

Success Bot Says

mordred on #openstack-sdks: “Finished the shade transition to pure REST away from client libs” [0]

Tell us yours in OpenStack IRC channels using the command “#success <comment>”

More: https://wiki.openstack.org/wiki/Successes

[0] – http://eavesdrop.openstack.org/irclogs/%23openstack-sdks/%23openstack-sdks.2017-12-04.log.html

Community Summaries

TC report 50 [0]

POST /api-sig/news [1]

Release countdown [2]

Technical Committee Status Update [3]

Resource Providers Update 45 [4]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2017-December/125434.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2017-December/125605.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2017-December/125610.html
[3] – http://lists.openstack.org/pipermail/openstack-dev/2017-December/125610.html
[4] – http://lists.openstack.org/pipermail/openstack-dev/2017-December/125643.html

Switching to Longer Development Cycles

Our self-imposed rhythm no longer matches our natural pace. Our elections, feature freezes feel like they’re around the corner, and due to that, we’re losing time from them, as multiple people have stated. The pace was designed around more people contributing full time to OpenStack, but lately, we have composite jobs, or were participating in multiple communities (which is great!).

It means:

One OpenStack coordinated release per year.

Maintain one stable branch per year.

Elect PTLs once a year.

One set of community goals per year.

One PTG per year.

Any project that still wants to release often can use the cycle-with-intermediary release model [0]. At a minimum, we’ll release once a year. Teams can choose to revive midcycle if they need to meet more than the one PTG each year. We’ll have more time for community-wide goals, so we will have more time to complete or even set more ambitious goals.

This doesn’t simplify upgrades. While upgrading every year is incrementally better than being forced to upgrade every 6 months. The real solution is better support for skipping releases.

It also doesn’t give us LTS. The cost of maintaining branches is not really due to the number of them in parallel, it’s due to the age of the oldest one. The real solution here is being discussed by the (still forming) LTS SIG. Extending stability periods is per-project at this point, and the proposal has yet to address a coordinated stability period.

We’re doing a year because of the way the events are organized. It’s suggested to start for the Rocky release and have the single PTG in 2018 in Dublin. The release team is opening the discussion to the community, and the TC will give a final decision.

Various cons were expressed, like this causing a rush to get in code at the end of a release to avoid having to wait an entire year. Projects are also forced to do compatibility support for versioned APIs, config files, etc since projects would be unable to drop compatibility in an intermediate release. Projects like Grenade will have to support the cases of some projects doing intermediate releases, and those doing yearly.

For the people that spend 20% of their time contributing to OpenStack, it has been voiced that it takes time to get a feature merged and the current cycle makes it impossible. This longer development cycle could help with allowing more time for those people. Various people expressed that we should be looking at the root cause of helping our part-time contributors, as the length of the cycle is unlikely the cause. People who can only contribute 20% of their time are also likely to deal with rebase conflicts, instead of focusing on their code.

Having a year could also impose having intermediate releases so specifications that can have multiple times a year to be approved. If that’s the idea, however, then it’s causing stress on the core team by having to match these precise schedules, in which the proposal was aiming to ease. It was a concern that this more solves the problem of giving more opportunities to people to get their spec/new feature considered.

This topic has also been brought up by various times in the past. Someone noted Daniel Berrange’s thread [1]

[0] – https://releases.openstack.org/reference/release_models.html#cycle-with-intermediary
[1] – http://lists.openstack.org/pipermail/openstack-dev/2015-February/057614.html

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-December/thread.html#125473

Zuul Dashboard Available

In addition to the Zuul dashboard [0] showing the “Status”, there are additional tabs added. “Jobs” page shows a list of all jobs in the system and their descriptions. The “Builds” page lists the most recent runs. You can query pipeline, job, and project.

[0] – http://zuulv3.openstack.org

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125384.html

Security SIG

Following previous mailing list discussions [0], the Security Project will be changing into a Special Interest Group (SIG). SIGs have shown to be a good match for the activity the group does around a topic or practice that spans around the community of developers, operators, and users. The group will continue to manage and care for the Security Guide, OSSNs, Bandit, Thread Reviews, Syntribos as well as encourage and incubate new security projects. The group will continue to work with the VMT and will keep a Sec-core group for launchpad that can work with the embargoes issues.

[0] – http://lists.openstack.org/pipermail/openstack-dev/2017-October/124053.html

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125607.html

Cycle Highlights Reminder

As we get closer to Queens-3 and our final RCs, a reminder is given about the new ‘cycle-highlights’ that has been added to deliverable info. Background of why this was added, some PTLs were being pinged multiple times every release cycle by various people like journalists, product manager and other to compile the same information. To mitigate that, we have a way to capture highlights as part of the release. This will give basic information, but not as a complete marketing message.

This is done in the openstack/releases repository in the deliverables/queens/$PROJECT.yaml file formatted like so:
    cycle-highlights:
        – Introduced new service to use the unsed host to mine bitcoin.

We have three different places that document activities for three different audiences:

Commit messages: Developer documentation
Release notes: End-user and deployer documentation
Cycle highlights: Journalists, product manager, and others.

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html

Community Goals For Rocky

Some questions to ask ourselves: What common challenges do we have, and who is willing to drive that community-wide goal (aka champion).

A champion is someone who drives a goal but doesn’t commit to writing code necessarily. The champion will communicate with project PTLs about the goal, and make the liaison if needed.

The list of ideas for community-wide goals is collected on this etherpad [0]. Propose some ideas now!

[0] – http://etherpad.openstack.org/p/community-goals

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125648.html

Quelle: openstack.org