| Slitaz 4.0 and some suggestions. |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/slitaz Archives
]
- To: slitaz <slitaz@xxxxxxxxxxxxxxxxxxx>
- Subject: Slitaz 4.0 and some suggestions.
- From: Alexander Medvedev <devl547@xxxxxxxxx>
- Date: Thu, 4 Aug 2011 11:58:55 +0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=OH6SDX6n2QVd5RN5qeF1W0Acy2TbHUmPEd8ZnjGNycE=; b=p0wiHH65j1nxWWnBW3XR9yet3mT29yUHmuxpGOoonq597StFBXmn1GOU3jrAKFAm9q gja2GaXeaepB26GEFlAb+G3HDz/4balToCzu9KGbeDOYuU3t9MSUHcwCcTpP4JmMAkgD Jt3z5w+lyAIQeBT64BpLYwx0wDWdqrDJmz1zY=
Any ETA for RC at least? What stops us from releasing it?
Also, may I suggest switching to a lot more convenient way of dealing with releases?
Why do we need to freeze cooking between releases? Why not keep it always-unstable rolling-release branch like gentoo ~arch or debian sid.
Before the release we just clone a cooking repo, clean all the bugs (bugfixes also go to cooking and vice-versa, but package versions are frozen), prepare RC and later replace stable with it.
It allows us to keep software updated and continue adding new packages to repos (having local testing repos is not that good - hard to share your work with others).
With best regards, Alexander.