1 |
Hey, |
2 |
|
3 |
Just read the last flurry of mails and will try to respond with my own |
4 |
opinions: |
5 |
|
6 |
I'm not a big fan of the "Gimp 1.2 -> 1.3 -> 1.4" style version tracking. |
7 |
It will add a lot of overhead, and point-releases with new problems are |
8 |
what we're desperately trying to avoid in the first place. Often times, |
9 |
stable releases of "major" revisions (IE: BIND 8 -> BIND 9) provide much |
10 |
less potential problems after initial migration. You also end up with a |
11 |
system much like redhat's. Half of it is more up to date than it should |
12 |
be, and the other half is frustratingly missing very helpful features. |
13 |
|
14 |
The idea of having a stable branch for enterprise installs isn't just so |
15 |
"once it's set up it'll be stable", but remember that you're not always |
16 |
the only person working on your network. Most of my coworkers here operate |
17 |
totally on their own. I would much prefer that they take a general build |
18 |
of gentoo from whereever, and have the same install as all of the systems |
19 |
I set up. Yes, I can set up a big complicated gold server with my own |
20 |
mirrors and such, but if they ever need something outside of that, it'll |
21 |
get ugly. Not only that, but often folks can't even budget the time to set |
22 |
things up right in the first place (including myself!). This |
23 |
gives people with anal-retentive PHB's a chance to put a stable |
24 |
gentoo-based operating system on their servers without a huge amount of |
25 |
work. Since it's perfectly possible to "freeze" your own stable tree and |
26 |
maintain it given current tools, the whole frozen tree idea wouldn't be on |
27 |
the table if there were outside requirements like this. |
28 |
|
29 |
Supporting ebuilds two years back with backports? I'm not sure. We have a |
30 |
*lot* of major databases here running solaris 2.6. Even with the latest |
31 |
patch clusters, latest "versions" of everything for solaris 2.6... They |
32 |
run with considerably more problems than the sol 8 or sol 9 machines. Even |
33 |
though basic bug and security fixes are backported, there are still major |
34 |
flaws in the system which were fixed by doing *major revisions*. A year is |
35 |
much more acceptable without crufting the system beyond usefulness. If you |
36 |
really think your sol 2.6 box is all that hot, I can pretty much assure |
37 |
you, you aren't using it much. |
38 |
|
39 |
Three year release cycles are beyond most major scopes of usefulness for |
40 |
anything other than appliances and possibly firewalls. I would much rather |
41 |
have focus on frozen quarterly branches with major stability |
42 |
fixes/security updates. That's the big thing, in my humble opinion, which |
43 |
would help break gentoo into the true enterprise of people having not |
44 |
enough time and admins not always being coordinated to the fullest. |
45 |
|
46 |
So yeah. Quarterly releases, security patches/backports up to a year back |
47 |
at most, and whatever else was listed. I can't remember the rest of the |
48 |
original e-mail anymore. |
49 |
|
50 |
have fun, |
51 |
-Dormando |