Excerpts from Steven Dake (stdake)'s message of 2016-10-07 20:39:04 +0000: > Doug, > > We have already tagged rc1 long ago, but ack on rc2 (we are targeting 12th at > present) and ack on 20th for retag of final rc. We expect our rc2 to be > final.
Right, I should have phrased that as a deadline for anyone who hadn't already tagged RC1. > If there are critical bugs that make the release doa in some way (such as > upgrades, reconfigure etc), we will obviously have to tag an rc3 to then > retag that as final. I don’t expect that to happen but it is a possibility. That's consistent with what we do for the milestone-based projects. Doug > > Regards > -steve > > > From: Doug Hellmann <d...@doughellmann.com> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: Friday, October 7, 2016 at 12:16 PM > To: openstack-dev <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] > proposed deadlines for cycle-trailing projects > > This week we tagged the final releases for projects using the > cycle-with-milestones release model. Projects using the cycle-trailing > model have two more weeks before their final release tags are due. In > the time between now and then, we expect those projects to be preparing > and tagging release candidates. > > Just as with the milestone-based projects, we want to manage the number, > frequency, and timing of release candidates for cycle-trailing projects. > With that in mind, I would like to propose the following rough timeline > (my apologies for not preparing this sooner): > > 10 Oct -- All cycle-trailing projects tag at least their first RC. > 13 Oct -- Soft deadline for cycle-trailing projects to tag a final RC. > 18 Oct -- Hard deadline for cycle-trailing projects to tag a final RC. > 20 Oct -- Re-tag the final RCs as a final release. > > Between the first and later release candidates, any translations and > bug fixes should be merged. > > We want to leave a few days between the last release candidate and > the final release so that downstream consumers of the projects can > report issues against stable artifacts. Given the nature of most > of our trailing projects, and the lateness of starting to discuss > these deadlines, I don't think we need the same amount of time as > we usually set aside for the milestone-based projects. Based on > that assumption, I've proposed a 1 week soft goal and a 2 day hard > deadline. > > Let me know what you think, > Doug > > Newton schedule: https://releases.openstack.org/newton/schedule.html > __________________________________________________________________________ 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
