On Wednesday January 10, 2001 23:22, Jordan Hubbard wrote:
> > Actually it says right now on http://www.freebsd.org/releases/
> > that 4.3 will be available in late March. It seems unusual that
> > such a precise time would be placed on the release already. I
> > think the date
>
> Not really. We schedule the releases for every 4 months, that being
> 3 a year, and they thus fall on predictable months (the day is a
> little more loose, usually specified with no more than 2 weeks
> precision).
Good to know. Sorry for the slightly off topic reply to -stable now.
I was going by the fact that the date for 4.2 was not mentioned on the
website (even though I had seen it mentioned in the mailing lists), nor
was the date for 4.1.1 I realize 4.1.1 was a special case.
While I knew releases happen fairly regularly, I had never seen a date
posted on the website this far in advance. Obviously with the CVS
repository of the webpages I could be proved even further wrong
possibly, but why would anybody do that? :~)
And to further promulgate my mistake in the archives, I'll add a
question. Is there any chance of a longer release candidate stage?
More testing and bug fixing would lead to a more stable system, one
would hope. Or is the release candidate too disruptive to stable
anyway? Is there a way to separate of the release candidate and lift
the stable freeze while the release candidates are tested further?
Obviously I'm showing my ignorance of how this process works now by my
questions, but oh well. :)
Tim
> The schedule is set on a date vs feature basis because the former
> practice leads to a better track record in getting releases out on a
> timely basis and because if you want to do things like provide CD
> media, you need to pre-schedule time with the CD replicators and they
> don't work to fuzzy schedules.
>
> That said, a release has been known to be delayed or even cancelled
> due to some major problem, but that's a rare event and one which will
> hopefully remain so.
>
> - Jordan
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
