Things to do before publishing a new version.

• 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:

  # tazlito pack-flavor core
  # tazlito get-flavor core
  # tazlito gen-distro

• 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.

• 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.
• 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.
• 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 …
• 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.

SliTaz stable release provides the release notes on the LiveCD through the package slitaz-doc, the repos are tagged just before release and are archived on the mirror. After the wok has been copied to wok-stable, the docs are back to a cooking cycle and just provide an index with basic information. On the system, docs are located in /usr/share/doc/slitaz, a desktop file and icon are provided in the sources package and can be used to have quick access to the documentation.

• SliTaz Doc repo