-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Keith Whitwell wrote: > On Tue, 2009-09-22 at 13:46 -0700, Ian Romanick wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I would like to open XDC by shipping Mesa 7.5.2 and 7.6. In order to >> make that happen, I propose the following: >> >> - - Freeze both branches at 12:01AM PDT 9/25 (this upcoming Friday). >> >> - - I will tag both trees at that time. One will get mesa_7_5_2_rc1, and >> the other will get mesa_7_6_rc1. >> >> - - Once those tags appear, please test whatever drivers *you* care about >> on whatever platforms *you* care about. >> >> - - Report any new regressions to bugzilla. If you find something that >> you believe is an absolute show stopper, mark it as such. We'll discuss >> whether we want to block the releases for it. >> >> For 7.6, I want to set the bar for blocking the release very, very high. >> At least one distro really wants to use 7.6, and their freeze is >> perilously soon. IMO, pretty much only build failures or "7.6 make my >> computer catch on fire, but 7.5.1 does not" are blockers. >> >> I had intended to post this RFC quite some time ago, but life issues >> outside of $JOB have distracted me for the last few weeks. The time has >> just slipped by. Aside from the absurdly compressed schedule, this >> seems to be what most other projects do, and I think Mesa should to. >> We've partially done this in the past, but our process could use a >> little more, well, process. :) > > I like the idea of better defining what our releases mean and how we get > there, and doing this freeze now seems pragmatic.
To be perfectly honest, I'm being a bit selfish. :) I want my QA to start their testing with the code that will hopefully be the release. Since they are in China, they have a big holiday starting October 1st. That gives them a hard limit on when they can start (and finish) testing. I was pretty sure that if I reminded people that we were intending to release at XDC there would be a pile of commits over the weekend. > However, next time round, a bit more time in the schedule would probably > be appreciated, so that people can schedule time for testing and/or > fixing the bugs that testing identify. Absolutely! In the next releases (both 7.6.1 and 7.7), I'm hoping we'll have some discussion about when the release candidates and freezes will happen. I had intended to have those discussions for this release. However, my wife broke her leg at the start of August, and in the process of taking care of her, the weeks just flew by. My brain still thinks it's August, not the last week of September. > If I understand things correctly, this is (or should be) the last 7.5.x > release, and that branch will more or less go to sleep after this? That's the intention. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkq6bO8ACgkQX1gOwKyEAw/VGgCgh3BopVH92nloNiaZf80gswFZ Iy8AmgKqKITFkDlTiifQO3Fj9QJqLq9Q =jf4F -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
