| From | Sent On | Attachments |
|---|---|---|
| 160 earlier messages | ||
| Mike Meyer | Jan 19, 2012 6:56 pm | |
| Da Rock | Jan 19, 2012 11:32 pm | |
| Mark Linimon | Jan 20, 2012 12:28 am | |
| Mark Linimon | Jan 20, 2012 12:58 am | |
| Alexander Leidinger | Jan 20, 2012 2:51 am | |
| Gleb Smirnoff | Jan 20, 2012 5:38 am | |
| Damien Fleuriot | Jan 20, 2012 5:43 am | |
| Gleb Smirnoff | Jan 20, 2012 5:59 am | |
| Damien Fleuriot | Jan 20, 2012 6:26 am | |
| Freddie Cash | Jan 20, 2012 9:57 am | |
| Chris | Jan 20, 2012 1:24 pm | |
| Daniel Gerzo | Jan 20, 2012 5:07 pm | |
| Mark Linimon | Jan 21, 2012 9:48 pm | |
| Mark Linimon | Jan 21, 2012 9:56 pm | |
| Peter Jeremy | Jan 21, 2012 11:12 pm | |
| Adrian Chadd | Jan 21, 2012 11:45 pm | |
| Da Rock | Jan 22, 2012 3:31 am | |
| Chris Rees | Jan 22, 2012 4:43 am | |
| Da Rock | Jan 22, 2012 5:14 am | |
| Robert Huff | Jan 22, 2012 6:39 am | |
| rank...@gmail.com | Jan 22, 2012 8:01 am | |
| Andrey Fesenko | Jan 22, 2012 8:35 am | |
| Devin Teske | Jan 22, 2012 8:41 am | |
| rank...@gmail.com | Jan 22, 2012 9:10 am | |
| Nathan Whitehorn | Jan 22, 2012 9:16 am | |
| Mark Linimon | Jan 22, 2012 9:20 am | |
| vermaden | Jan 24, 2012 3:23 am | |
| Arnaud Lacombe | Jan 24, 2012 10:35 am | |
| Chris Rees | Jan 24, 2012 11:51 am | |
| Mark Linimon | Jan 24, 2012 1:09 pm | |
| Mark Linimon | Jan 24, 2012 1:23 pm | |
| Arnaud Lacombe | Jan 24, 2012 1:33 pm | |
| Mike Meyer | Jan 24, 2012 2:09 pm | |
| vermaden | Jan 24, 2012 3:05 pm | |
| Mike Meyer | Jan 24, 2012 3:35 pm | |
| vermaden | Jan 24, 2012 10:36 pm | |
| Don Lewis | Jan 24, 2012 11:14 pm | |
| Mark Linimon | Jan 24, 2012 11:27 pm | |
| Arnaud Lacombe | Jan 25, 2012 12:58 am | |
| Davide Italiano | Jan 25, 2012 1:08 am | |
| Mark Linimon | Jan 25, 2012 12:22 pm | |
| Arnaud Lacombe | Jan 25, 2012 2:26 pm | |
| Da Rock | Jan 26, 2012 3:45 am | |
| John Baldwin | Jan 26, 2012 6:37 am | |
| Mark Blackman | Jan 26, 2012 8:48 am | |
| John Baldwin | Jan 26, 2012 10:22 am | |
| Mark Blackman | Jan 26, 2012 2:23 pm | |
| Mark Linimon | Jan 26, 2012 2:48 pm | |
| Mark Blackman | Jan 26, 2012 2:52 pm | |
| Rick Macklem | Jan 26, 2012 6:18 pm | |
| Mark Linimon | Jan 26, 2012 7:25 pm | |
| Mark Blackman | Jan 27, 2012 4:01 am | |
| John Kozubik | Feb 8, 2012 10:33 pm | |
| md...@FreeBSD.org | Feb 8, 2012 11:08 pm | |
| Da Rock | Feb 9, 2012 5:23 am | |
| rank...@gmail.com | Feb 14, 2012 9:18 am | |
| Mark Linimon | Feb 18, 2012 2:16 pm | |
| Super Bisquit | Feb 18, 2012 3:28 pm | |
| Subject: | Re: FreeBSD has serious problems with focus, longevity, and lifecycle | |
|---|---|---|
| From: | Rick Macklem (rmac...@uoguelph.ca) | |
| Date: | Jan 26, 2012 6:18:14 pm | |
| List: | org.freebsd.freebsd-hackers | |
Mark Blackman wrote:
On 26 Jan 2012, at 14:37, John Baldwin wrote:
On Thursday, January 19, 2012 4:33:40 pm Adrian Chadd wrote:
On 19 January 2012 09:47, Mark Saad <none...@longcount.org> wrote:
What could I do to help make 7.5-RELEASE a reality ?
Put your hand up and volunteer to run the 7.5-RELEASE release cycle.
That's not actually true or really fair. There has to be some buy-in from the project to do an official release; it is not something that a single person can do off in a corner and then have the Project bless the bits as an official release.
And raises the interesting question for an outsider of
a) who is "the project" in this case and b) what does it take for a release to be a release?
Wasn't there a freebsd-releng (or similar) mailing list ages ago?
I am going to avoid the above question, since I don't know the answer and I believe other(s) have already answered it.
However, I will throw out the following comment: I can't seem to find the post, but someone suggested a release mechanism where stable/N would simply be branched when it appeared to be in good shape. Although I have no idea if this is practical for all releases, it seems that it might be a "low overhead" approach for releases off old stable branches like stable/7 currently is? (ie. Since there aren't a lot of commits happening to stable/7, just branch it. You could maybe give a one/two week warning email about when this will happen. I don't think it would cause a "flurry of commits" like happens when code slush/freeze approaches for a new .0 one.)
Just a thought, rick
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "free...@freebsd.org"





