On 12/14/2016 03:21 PM, Emilien Macchi wrote: > On Tue, Dec 13, 2016 at 5:02 PM, Emilien Macchi <emil...@redhat.com> wrote: > > I thought it would be useful to share our roadmap for TripleO releases. > > As a reminder, this is the official source of trust for OpenStack > > releases schedule: > > https://releases.openstack.org/ocata/schedule.html > > > > Over the last weeks, we discussed about how TripleO project would > > produce better releases without stressing people at pushing for > > features late in cycles. > > > > - tripleo-specs for Ocata need to be merged by ocata-2 or will be > > postponed to Pike. > > - blueprints scheduled for ocata-2 with good progress will be > > postponed to ocata-3. > > done. Though I found 44 blueprints for ocata-3 too big, we'll review > them and eventually postpone some of them, as this number doesn't > sound realistic. > > > - blueprints scheduled for ocata-2 with zero or low progress will be > > postponed to pike-1. > > I did that operation today. Please let me know if you disagree if your > blueprint moved to pike-1 and we can discuss about it. > > > - we'll release ocata-2 end of this week. > > done: https://review.openstack.org/#/c/410958/ > > > - we'll release a new Newton release next week. > > - by the end of ocata-3, we'll stop pushing for features except > > Composable Upgrades which is our critical thing during this cycle. > > Anything else will be frozen and postponed to Pike. > > - we'll threat FFE case by case but if the FFE is not related to a > > blueprint that was targeted for ocata-3, no need to ask, it will be > > rejected. > > - between end of ocata-3 and final ocata release, we have 5 weeks. We > > might want to spend time on stabilization, bug fixing (we currently > > have more than 100 bugs open, just for ocata-2) and keep CI stable > > until final release. The last thing we want is to push for last > > features and stress people because it breaks all the things. > > > > Please provide any feedback, it's highly welcome. > > -- > > Emilien Macchi > > > I'll be going through and moving a bunch to Pike soon as well.
-J -- Jason E. Rist Senior Software Engineer OpenStack User Interfaces Red Hat, Inc. Freenode: jrist github/twitter: knowncitizen __________________________________________________________________________ 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