Downtime?
in [Slackware]
|
From: Henrik Carlqvist on 8 Mar 2010 13:35 Eric Hameleers <eric1(a)sox.homeip.net> wrote: > Manuel Reimer schreef: >> Does anyone know what's going on? > Yes. You obviously know more about this than most of us. Would you give any comment about the 13.1 directory next to the 13.0 directory in http://connie.slackware.com/~alien/multilib/ ? Does the 13.1 directory mean that slackware-current now is soon to be 13.1? regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost
From: Michael Black on 8 Mar 2010 14:11 On Mon, 8 Mar 2010, Henrik Carlqvist wrote: > Eric Hameleers <eric1(a)sox.homeip.net> wrote: >> Manuel Reimer schreef: >>> Does anyone know what's going on? > >> Yes. > > You obviously know more about this than most of us. Would you give any > comment about the 13.1 directory next to the 13.0 directory in > http://connie.slackware.com/~alien/multilib/ ? Does the 13.1 directory > mean that slackware-current now is soon to be 13.1? > I thought he was making a joke, that someone does know what's going on, not necessarily him. Slackware-current is bound to be 13.1, I can't imagine them kicking it up further. I'm not sure that's the directory to watch for indications of a new release. The changelog doesn't yet have the key part someone suggested was the mark of an impending release. Note that poor aaa_elflibs has gone through 3 updates since the end of January (one on Jan 24, then on the big update of March 1st and then another update a day or so later). Even if everything is up to date, things are still shaking out, you go a month between changelog entries and that's bound to cause secondary things (some already found) that have to be found before it can even be considered "stable". When a new release comes is pretty vague, something like "yes we know there will be another release at some point", but it's a moving point, and I think they toss dice or something to get the exact release. What's about to be updated that's worth waiting for? What won't they bother with because it will be too new and untested? Some packages go through a few iterations between Slackware releases, and Slackware follows so depending on the importance of the package each may call for further delays as other things have to be updated too. Yesterday there were some kernel rebuilds, the followup to the March 1st updates. But that's not necessarily an indication of a new release, it may just be keeping up with the kernel. Meanwhile, it requires actual uses to bash it to pieces in order to see if everything fits together. There have been some comments here, and the changelog has already reflected some of that (though it's not clear if it's a result of the issues brought up here, or if others brought it up to Slackware more directly). Besides, the final major indication of a new release is the call for guesses on when the next release will be. Until that happens, there will not be a new release. Michael
From: .Martin. on 8 Mar 2010 14:49
Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> writes: > Eric Hameleers <eric1(a)sox.homeip.net> wrote: >> Manuel Reimer schreef: >>> Does anyone know what's going on? > >> Yes. > > You obviously know more about this than most of us. Would you give any > comment about the 13.1 directory next to the 13.0 directory in > http://connie.slackware.com/~alien/multilib/ ? Does the 13.1 directory > mean that slackware-current now is soon to be 13.1? > > regards Henrik I wouldn't expect it to be very, very soon. There were some big changes in the previous update of -current. Now I'd imagine it needs to be properly tested for some time. -- regards ..Martin. |