On Sat, Aug 29, 2009 at 05:17:06PM -0700, Doug Barton wrote:
Howdy,
I make this suggestion every time there is a new major release coming,
maybe this time will be the one! :)
One could argue that with the 2 active stable branches that we have
now the freebsd-stable@ mailing list is
On Sat, 29 Aug 2009 20:17 -, dougb wrote:
Howdy,
I make this suggestion every time there is a new major release coming,
maybe this time will be the one! :)
One could argue that with the 2 active stable branches that we have
now the freebsd-stable@ mailing list is already quite confusing.
On Sat, 29 Aug 2009 20:17 -, dougb wrote:
Howdy,
I make this suggestion every time there is a new major release coming,
maybe this time will be the one! :)
One could argue that with the 2 active stable branches that we have
now the freebsd-stable@ mailing list is already quite confusing.
CmdLnKid wrote:
On Sat, 29 Aug 2009 20:17 -, dougb wrote:
Howdy,
I make this suggestion every time there is a new major release coming,
maybe this time will be the one! :)
One could argue that with the 2 active stable branches that we have
now the freebsd-stable@ mailing list is already
Hi,
Thus, my suggestion. Split what is currently freebsd-stable into one
list per branch.
We could also THINK about whether we want more than 1 stable branch, which
is the true case now.
Either we relese too often or older releases have a far to long lifecycle
before reching EOL.
Recalling
On Sat, Aug 29, 2009 at 8:17 PM, Doug Barton do...@freebsd.org wrote:
...
Thus, my suggestion. Split what is currently freebsd-stable into one
list per branch. This year I even have a better suggestion for the
names, freebsd-6@, freebsd-7@, and freebs...@. After the flag day mail
sent
