Hi,
I open this topic because public discussion need about development strategy of SliTaz.
At first, thanks at all developpers take free time to invest in project.
Today we have :
stable aka 4.0, very old
cooking (future 5.0), follow rolling release model.
Due of age of 4.0, more users use cooking as "stable" system.
With this, we lost workflow of "staging" zone between development and stable release.
I don't blame anyone, update of packages in cooking can and unfortunally break many packages.
I suggest setting up a "testing" environment but before we need focus on release stable.
In other topic gibor talk about upgrade gcc version, and agree with it, it's time to achieve goal of upgrade SliTaz.
It's no easy, but i think with all developpers and help of community we can define milestone and keep SliTaz, best small and up to date system.
Main reason last year i purpose sponsor and host gracefully, i absolutely don't want to see the project die.