Eric Kow writes: > On Tue, May 11, 2010 at 11:29:32 +0000, Ben Clifford wrote: > > > 2) We can catch some nasty platform-related last-minute bugs. This is > > > particularly valuable on minor releases, that don't get the usual "RC" > > > treatment. > > > > What happens if (eg) 2.4.4 has a bug in it? Don't release 2.4.4 to the > > general public, and they must wait until 2.4.5? or make another 2.4.4 so > > that there are multiple 2.4.4s floating around behaving differently, with > > no way to tell them apart version-wise? > > I think for maximum clarity, it would be wait until 2.4.5
Then there should not be a long wait until 2.4.5. Probably 2.4.5 should be released as source as soon as the bug is confirmed fixed. But effectively this demotes the released version to an RC anyway. I think the best way to handle it is to have one source-only RC, with no changes allowed except fixes for show-stoppers (which requires another RC) and in the release, change the version from RC to release. _______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
