Welcome to our regular release countdown email!

Development Focus

Teams should be wrapping up Pike-1 work.


Next week is the Pike-1 deadline for cycle-with-milestones projects.
That means that before EOD on Thursday all milestone-driven projects
should propose a SHA for Pike-1 as a change to the openstack/releases
repository. As a reminder, Pike-1 versions should look like "P.0.0.0b1"
where P = Ocata version + 1. So if your Ocata release was "5.0.0",
Pike-1 should be "".

Pike-1 also marks the deadline for switching release models, as well as
submitting your team responses to the Pike release goals[1]. Responses
to those goals are needed even if the work is already done. At this hour
we seem to still be missing some (or all) answers from cinder,
cloudkitty, congress, designate, docs, dragonflow, ec2api, freezer,
fuel, heat, horizon, infra, karbor, kolla, kuryr, magnum, manila,
mistral, monasca, murano, neutron, nova, octavia, charms,
OpenStackAnsible, OpenStackClient, oslo, packaging-deb, packaging-rpm,
rally, refstack, requirements, sahara, searchlight, security, senlin,
solum, swift, tacker, telemetry, tricircle, trove, vitrage, watcher,
winstackers, and zaqar.

[1] https://governance.openstack.org/tc/goals/pike/index.html

Upcoming Deadlines & Dates

TC election self-nomination: April 9
Pike-1 milestone: April 13
Forum at OpenStack Summit in Boston: May 8-11

Thierry Carrez (ttx)

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to