Release planning for 2.063

[Nick Sabalausky]

On Mon, 25 Feb 2013 19:47:19 +0100
Johannes Pfau <nospam at example.com> wrote:

> As there were complaints about not having a release schedule for 2.062
> and releases being made suddenly without no prior announcement

I'm not sure where people are getting that idea. There's *always* prior
notice:

http://forum.dlang.org/post/5114B7A5.40102@digitalmars.com

And that's been a regular thing for a least a couple years.

Granted, there probably *should* be an additional announcement made on
D.announce when a beta period starts. And the dmd-beta list
*really* needs to be converted to a proper newsgroup. Having it as a
mailing list is just ridiculous.

But even things are, there certainly isn't "no prior announcement".


> I propose to do the feature freeze next Monday (no more new features
> after that). At the same time the first beta is released. Then 2 weeks
> later first release candidate, one week later the next release
> candidate and one more week to the final release:
> 
> Feature freeze     4 mar 2013
> Beta 1             4 mar 2013
> RC 1               18 mar 2013
> RC 2               25 mar 2013
> Final release      1 apr 2013 
> 

Scheduling RCs and finals is a bad idea, and so is locking the number
of RCs. RCs and finals need to come *as* problems found with the beta
and subsequent RCs are fixed. If that ends up taking more or less
time than some completely arbitrary predetermined "fits all sizes"
length of time, then so be it. What you're proposing is just scheduling
for sake of scheduling. It's just arbitrary red tape, it doesn't help
anything.