SEO

#1 (**permalink**) 03-09-2008, 01:36 PM

The aim of current is to be the next release, and I do not understand
some points:

* Why PV has upgraded the toolchain (glibc, binutil, gcc) _after_ the
non-essential packages?
* He had upgraded the kernel to 2.6.23.16. Some people tested *this*
particular kernel branch. Now, there is 2.6.24 in -current! A big step.

I don't want to say it's bad, it just seems illogical.

--
On dira ce qu'on voudra, j'étais pas un petit loubard comme les autres.
(Rocky)

#2 (**permalink**) 03-09-2008, 01:36 PM

On Sat, 08 Mar 2008 12:06:14 +0100, ciol wrote:

> The aim of current is to be the next release, and I do not understand
> some points:
>
> * Why PV has upgraded the toolchain (glibc, binutil, gcc) _after_ the
> non-essential packages?
> * He had upgraded the kernel to 2.6.23.16. Some people tested *this*
> particular kernel branch. Now, there is 2.6.24 in -current! A big step.
>
> I don't want to say it's bad, it just seems illogical.

I don't speak for Slackware[0] but this is what I have noticed over the
years.

After a release -current is pretty stable
then after some time it becomes unstable, sometimes it fluctuates back
and forth between stable and unstable
Before the next release it starts to become stable again

My belief is that in order for PV to add new software into Slackware he
has to take risks. These risks often lead to an unstable -current. Once
all the instability has been ironed out a new Slackware is released with
new software that is stable.

Richard James

[0] Just the Hamsters
--
clueless adjective
(informal) stupid.
(usenet) Tom Newton

#3 (**permalink**) 03-09-2008, 01:36 PM

Richard James wrote:

> On Sat, 08 Mar 2008 12:06:14 +0100, ciol wrote:
>
>> The aim of current is to be the next release, and I do not understand
>> some points:
>>
>> * Why PV has upgraded the toolchain (glibc, binutil, gcc) _after_ the
>> non-essential packages?
>> * He had upgraded the kernel to 2.6.23.16. Some people tested *this*
>> particular kernel branch. Now, there is 2.6.24 in -current! A big step.
>>
>> I don't want to say it's bad, it just seems illogical.
>
> I don't speak for Slackware[0] but this is what I have noticed over the
> years.
>
> After a release -current is pretty stable
> then after some time it becomes unstable, sometimes it fluctuates back
> and forth between stable and unstable
> Before the next release it starts to become stable again
>
> My belief is that in order for PV to add new software into Slackware he
> has to take risks. These risks often lead to an unstable -current. Once
> all the instability has been ironed out a new Slackware is released with
> new software that is stable.
>
> Richard James

>
> [0] Just the Hamsters

And further, PV allows us to test the software that will be in the next
release. This allows further bug finding, as you may observe by reading, in
full, the -current change log.

--
humjohn AT verizonf DOT net

#4 (**permalink**) 03-17-2008, 06:09 AM

On 2008-03-08, ciol <ciol13@gmail.com> wrote:
> The aim of current is to be the next release, and I do not understand
> some points:
>
> * Why PV has upgraded the toolchain (glibc, binutil, gcc) _after_ the
> non-essential packages?
> * He had upgraded the kernel to 2.6.23.16. Some people tested *this*
> particular kernel branch. Now, there is 2.6.24 in -current! A big step.
>
> I don't want to say it's bad, it just seems illogical.

Without going into great detail, I'll just say that decisions like
that are not made on a whim. There is lots of testing on a decent
variety of hardware taking place before stuff like that makes it
out to the public. Of course, that's no guarantee that there won't
be unforseen bugs, but when it passes the "works for us" test, there's
a better than average chance that it will work for everyone else too.

As an aside, you'll notice that 2.6.24.x has a *LOT* of additional
wireless support in it - that alone makes it a very desirable upgrade.

-RW

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

I don't understand -current development model