Welcome to our regular release countdown email! Development Focus -----------------
Teams should be working on specs approval and implementation for priority features for this cycle. Actions ------- Your team produces libraries, and some of them are still using a version <1.0 ? Now is a good time to look at those and move them to 1.0 (or define a time when they will be able to do so). A 0.x release implies something is not stable and each new release is likely to be a breaking change. Consumers are often reluctant to use libraries with version numbers like that. The sooner you can commit to an API and start fully using semver to signal change, the better! As a reminder, Pike-1 is coming up on R-20 week. Time is running out to propose a change in your release model: if you want to switch from cycle-with-milestones model to a cycle-with-intermediary model (or the other way around), propose a change to your Pike deliverable files at [1] now! [1] http://git.openstack.org/cgit/openstack/releases/tree/deliverables/pike Pike-1 is also the deadline for submitting your team responses to the Pike release goals[2]. Responses to those goals are needed even if the work is already done. You can find more information on the Goals process at [3]. [2] https://governance.openstack.org/tc/goals/pike/index.html [3] https://governance.openstack.org/tc/goals/ Upcoming Deadlines & Dates -------------------------- Boston Forum topic formal submission deadline: April 2 Pike-1 milestone: April 13 (R-20 week) 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 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
