Bering-uClibc 4.x - Developer Guide - The Release Process
|The Release Process|
|Prev||Bering-uClibc 4.x - Developer Guide|
The target audience for this page are LEAF maintainers and admins.
The page describes the release process, mostly as reminder. Note: Various steps require (different) admininstrator privileges.
Rebuild new release from source
It is recommended to do a completly fresh build from the sources. Create a new directory and copy buildtool the directory into it. Compile the build environment and all packages.
./buildtool.pl build buildenv tools/buildall.sh
Finally build the lwp files for webconf.
Commit Packages to SF SCM
Copy all generated lrp packages to [path to git]/leaf/bering-uclibc4/bin/packages. Commit and push into the git repository:
[path to git]/leaf/bering-uclibc4/bin/packages git commit * [path to git]/leaf/bering-uclibc4/bin/packages git push
Create images and source tarball
Create the images:
fakeroot ./buildimage.pl --image=Bering-uClibc_geode_syslinux_ser --relver 4.0-nn fakeroot ./buildimage.pl --image=Bering-uClibc_i486_isolinux_vga --relver 4.0-nn fakeroot ./buildimage.pl --image=Bering-uClibc_i486_syslinux_ser --relver 4.0-nn fakeroot ./buildimage.pl --image=Bering-uClibc_i486_syslinux_vga --relver 4.0-nn fakeroot ./buildimage.pl --image=Bering-uClibc_i686_syslinux_vga --relver 4.0-nn fakeroot ./buildimage.pl --image=Bering-uClibc_i686_isolinux_vga --relver 4.0-nn
It is a good idea to finally test the newly build version with qemu:
qemu-system-i386 -cdrom image/Bering-uClibc_i486_isolinux_vga/Bering-uClibc_4.0-nn_i486_isolinux_vga.iso
Create the sources tarball as required by SF policy:
cd [path to git]/leaf/bering-uclib4/buildtool$ tar cvf - * | gzip -9 -c - > [your/upload-dir]/Bering-uClibc_4.0-nn_src.tgz
Tag release in SCM
[path to git]/leaf/bering-uclibc4# git tag -a v4.0-nn [path to git]/leaf/bering-uclibc4# git push origin v4.0-nn
Clean up Trac
Edit the milestone in LEAF Trac and either close the active tickets or move them to later version.
Add the new release on the LEAF Trac - Versions page and select it as new "Default", so the new version will be the default version when creating a new ticket.
Create README and Announcement
Upload files to SF FRS
Login to SF FRS Create New Folder, named with the release version. Change to the created folder and upload Readme and all the images.
Create Packages page