New 2.6.0 naming

[nestu]

Moritz Heiber wrote:
[ ... ]
> So the list is:
> 
> 1) Test the new kernel, even be on the lookout for 2.6.1 (I expect it
> for mid January).
> 2) Integrate and test the new glibc.
> 3) Integrate and test the new (yet to come) Nvidia drivers.
> 4) Xfree? $ISSUE_WITH_2.6
> 5) Push it out.
> 
> Lets avoid all that "2.6 hype" and do some real testing on this new baby
> before getting it out.
2 things:
1) Personally I don't use NVidia drivers. Having said that, 
and as nasty it may seem (I swear I'm not) I think this is 
completely secondary. If NVidia doesn't get stuff working 
natively themselves or you have to use patches, it shouldn't 
affect any steps to take. I think the rest of Moritz's 
points are fine ;) Let's also see what happens with NTPL as 
elaine said ;)
2) Naming scheme is not going to change for now - I suppose 
you have already noticed the
module bump in moonbase. For the sake of simplicity keeping 
the name will be better, IMHO.
Later on, on a well tested kernel, ¿could we start a new 
naming system?. I like Ratler's idea on naming 24 and 26.
BTW, if Andrew Morton continues to add -mm patches, would 
you like them included? (as an option, for example)
CU,
nestu ;)))
-- 
Lunar Linux		http://www.lunar-linux.org
XFce Desktop		http://www.xfce.org
#OnlyLinux LUG		http://www.onlylinux.no-ip.org

QOT?:
<Veerappan> also, i'm upset.  my roommate's treadmill is too 
short.
<Veerappan> another foot, and my bike would fit :)