From: Brian P. <br...@vm...> - 2009-11-18 21:06:26
|
Ian Romanick wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Brian Paul wrote: >> Ian Romanick wrote: >>> As promised, I'm sending out a proposed release schedule before the 11th >>> hour. Doing a simultaneous x.y.z and x.y+1 release worked out pretty >>> well last time, so I propose to do the same thing again. The RC and >>> final dates below are for both 7.7 and 7.6.1. >>> >>> The RC1 date is pretty important as it aligns with at least one distro's >>> release schedule. >>> >>> Create mesa_7_7_branch 11/19 >>> RC1 11/30 >>> RC2 12/7 >>> RC3 12/14 >>> final 12/21 >>> >>> The goal is for RC3 and final to be the identical with the exception of >>> version strings and repository tags. >> It looks like mesa_7_7_branch has been created a day ahead of schedule. >> That's OK. > > Aw crap. I could have sworn that I put a date for Tuesday, but the 19th > is, in fact, Thursday. > >> I'd like to propose fast-tracking the 7.6.1 release to minimize the time >> during which we have to worry about having 3 active branches >> (mesa_7_6_branch, mesa_7_7_branch and master). >> >> The 7.6.1 release should be ready to go at any time since it's just bug >> fixes. So I'd like to make a release candidate today, and release 7.6.1 >> by the end of the week. >> >> Any objections? > > That should be fine. Do you have any proposed dates? 7.6.1 RC1 today, and if no issues pop up, do the final 7.6.1 release on Friday/Saturday. The 7.7 schedule looks OK, but I'd be happy to move up the final 7.7 release if the release candidates seem solid. -Brian |