I haven't been here for a little while, & I was wondering how SliTaz version 5 is coming along, (or not).
Is there any recent activity ?
I haven't been here for a little while, & I was wondering how SliTaz version 5 is coming along, (or not).
Is there any recent activity ?
Just in package updates and a few fixes to cooking. No official news on a SliTaz 5 release, although there have been several people that have been trying to push for a release.
Thanks for the info Trixar_za - I did grab a cooking dvd a few weeks ago.
> Is there any recent activity ?
... tons of it! Have a look here: http://hg.slitaz.org/?sort=lastchange
But I'm also wondering what technical reasons there are for the delay of a SliTaz 5 release? Except for the muddled boot options screen and the problems with udevil/SpaceFM, all the Rolling releases of the past 6+ months have been working without a hitch on my hardware. A while back Kultex has posted an ISO image with a tweaked kernel, which also worked without any problems. So, what's holding back 5.0? I read the debate in this forum and on the mailing list fairly regularly. Have I missed anything?
And now people are discussing a backport repo to give SliTaz 4 another lease of life. I think this is only a good idea and worth the effort if a SliTaz 5.0 release is indeed not even on the horizon. But is it?
There are several things that need to happen before we can release SliTaz 5. The first is that we need to create a package repository (split off current cooking) for it and then release a release candidate of SliTaz 5 configured to use it. The second step is to get people to test it and draw in developers to fix the bugs the testers identifies. After enough bugs have been fixed, we can release a second RC version for further testing and a second round of bug fixes. Once that's done and all the critical bugs have been fixed, we can finally release SliTaz 5 completely.
So, do we have any takers that want to get the ball rolling on this?
>So, do we have any takers that want to get the ball rolling on this?
Do we have enough developers to fix all bugs found? Some bugs are a couple year old :3
True. The only way a release will happen is if we pull some people into the project. Testers can be debuggers too, so it just needs somebody with repository commit access to apply it. I also think we should create a debug page just for testing SliTaz 5 RC, so we don't try fixing old bugs that aren't there anymore. I haven't really contributed much, so I'm willing to put in some debugging work once this gets started.
hi,
seems that these would be the main characteristics of SliTaz-5
* Binutils 2.23.1
* Linux API headers 3.2.40
* GCC 4.6.3
* Glibc 2.14.1
can anyone confirm?
Confirmed, although each one probably needs to be upgraded.
Les nouvelles versions attirent souvent de nouveaux développeurs.
Je suis d'accord avec Trixar_za pour la page de debug.
La vraie question est: la rolling est-elle suffisamment stable pour en faire un cooking ?
===
New versions often attract new developers.
I agree with Trixar_za for the debug page.
The real question is: the rolling is stable enough to make a cooking?
yes it is stable enough - I am running now my testing iso since more than 3 month without any problems
the only bug for me is in claws mail
before we make a RC1 I suggest following things:
Update:
claws-mail to 3.9.2 - is now 3.8.1
spacefm to 0.9.2 - is now 0.8.6
udevil to 0.4.3 - is now 0.4.0
wbar to 2.3.4 - is now 1.3.3
midori to 0.5.6-1 - is now 0.5.0
change the kernel config - I will look one more time into it and attach it the next days
it would be nice, if somebody can do it, as I have no hg access
EDIT: kernel is now 3.2.53 - I will look, if we need some more changes
Thomas
>although each one probably needs to be upgraded.
IMHO, we dont have enough people to work on both stable and rolling versions.
We are not debian or ubuntu, we dont need to mess with LTS versions. Why not keep everything updated to latest versions?
No. We don't have enough people and time.
The last cooking was published in 05/2011. In the past, before publishing some RCs, we used to do more cooking.
I think we must plublish at least one Cooking before starting RCs.
Updating some packages ? Why not if it does not break anything. In particular udevil and Midori.
@Kultex: Touch the kernel and toolchain involves too much change.
What changes have you made to the kernel configuration?
And we also have some packages to fix on the build host (http://cook.slitaz.org/)
@erjo
kernel issues are discussed starting from here
http://forum.slitaz.org/topic/notes-to-new-cooking/page/8
mainly I touched ide and scsi
if we would stay on the rolling kernel, there would be no ide CDs and DVDs as udev does not handle any more the old ide config and I included better scsi support (this effects only the linux-scsi.tazpkg) and some performance issues
the kernel works perfect - you can test it from here:
kultex: You may have to provide your udevil and sd[a-z][0-9] supported slitaz scripts.
You must log in to post.