Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision Last revision Both sides next revision | ||
en:cookbook:releasetasks [2010/02/18 22:01] jozee created |
en:cookbook:releasetasks [2012/02/17 19:59] pankso |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ~~NOTOC~~ | ||
====== Release tasks ====== | ====== Release tasks ====== | ||
Things to do before publishing a new version. | Things to do before publishing a new version. | ||
+ | <note>20120217 <pankso> Current Cooking stat is almost stable, we are ready for RC. The currents things to do are: | ||
+ | * Write the release notes in English here on the Wiki, them statis xHTML for translation on the list and commiting in slitaz-doc | ||
+ | * Improve start guide in slitaz.doc repo | ||
+ | * Update doc in this wiki. The Handbook must be ugely improved or removed since people use guides section (ex liveUSB have 2 pages...) | ||
+ | * Test new SliTaz installer: tazinst from cmdline and TazPanel (both new install and system upgrade) | ||
+ | </note> | ||
- | ===== Check list ===== | + | ===== Cooking & RC ===== |
+ | * Make sure all repos are tagued to include latest change and updated into the wok. | ||
+ | * make sure all packages are built on Tank, generate a new package list with cook and sync the mirror with: tazdev -p username | ||
+ | * Use a chroot and tazdev (or conspy -f 4 on Tank) to build ISO's | ||
+ | * IMPORTANT: Use the packages on mirror.slitaz.org to build the ISO's (rm -rf /home/slitaz/packages && tazpkg -cc) | ||
+ | * If flavors repos have been modified dont forget to update it in the chroot | ||
+ | * Build a core with Tazlito: <code> | ||
+ | # tazlito pack-flavor core | ||
+ | # tazlito get-flavor core | ||
+ | # tazlito gen-distro</code> | ||
+ | * Boot this ISO with Qemu, burn it to CD an boot, make a live USB and boot to make sure everything works. | ||
+ | * When on the desktop, try ALL desktop entries and a few commands or latest code. | ||
+ | * Connect to the web and install a few packages to test them | ||
+ | * IMPORTANT: Install to HD and reboot, users should got an X environemnt without any other modification. Installation and upgrade is realy important for 4.0 since we have a new installer. | ||
+ | |||
+ | |||
+ | ===== Stable ===== | ||
+ | |||
+ | * After some Cooking and a few RC | ||
* Release version is specified by ///etc/slitaz-release//, this file is controlled by slitaz-base-files. Base files are tagged just before a stable release to change the version string and let Tazpkg use the new packages. | * Release version is specified by ///etc/slitaz-release//, this file is controlled by slitaz-base-files. Base files are tagged just before a stable release to change the version string and let Tazpkg use the new packages. | ||
- | * Check that the SliTaz version specified in ///etc/issue// message is the same as displayed in isolinux.msg. | + | * Check that the SliTaz version specified in ///etc/issue// message is the same as displayed in isolinux.cfg for Vesa menu, here syslinux package must be modified. |
- | * Add and check that documents and images are in the root of the CD - ie. README, index.html, style.css and the directory of images. All files are in the slitaz-tools archive; just copy the //addfiles/// and regenerate the ISO. | + | * When all other repos are taggued like for a cooking, all packages update, we can tag the main wok. |
+ | * Remove the current stable wok and copy the cooking wok in place. | ||
+ | * Sync Tank with mirror | ||
+ | * Go on mirror and copy all cooking packages to the stable string. | ||
+ | * Remove stable string in cooking wok and slitaz-base-file repo (update it again) so it goes back to a normal stat and dev can start commiting. Toolchain update may be discuss at this moment. | ||
+ | * Build ISO's from a stable chroot or running system and use packages on the main mirror as usual. | ||
* Test, test, and test ... | * Test, test, and test ... | ||
* Prepare the website announcement and RSS feeds. The Mailing list is used for translation and any text should be submitted 1 or 2 days before release. | * Prepare the website announcement and RSS feeds. The Mailing list is used for translation and any text should be submitted 1 or 2 days before release. | ||
+ | |||
===== Stable documentation ===== | ===== Stable documentation ===== | ||
Line 16: | Line 47: | ||
* [[http://hg.slitaz.org/slitaz-doc/ | SliTaz Doc repo]] | * [[http://hg.slitaz.org/slitaz-doc/ | SliTaz Doc repo]] | ||
- | * [[http://labs.slitaz.org/wiki/slitaz-doc | SliTaz Doc on the Labs]] | ||