Difference between revisions of "Bering-uClibc 6.x - Developer Guide - The Release Process"
m (→Rebuild new release from source) |
|||
Line 23: | Line 23: | ||
To save time, it is also possible to blacklist packages that are known not to build or only necessaryfor special tasks (e.g. <code class="filename">valgrind.lrp<code>. | To save time, it is also possible to blacklist packages that are known not to build or only necessaryfor special tasks (e.g. <code class="filename">valgrind.lrp<code>. | ||
− | == | + | ==Sign packages with GPG maintainer key== |
− | + | tbd | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
==Create images and source tarball== | ==Create images and source tarball== | ||
Line 47: | Line 43: | ||
git archive --format=tgz -9 HEAD -o [your/upload-dir]/Bering-uClibc_6.0.0-nn_src.tgz | git archive --format=tgz -9 HEAD -o [your/upload-dir]/Bering-uClibc_6.0.0-nn_src.tgz | ||
− | ==Tag release in | + | ==Tag release in LEAF Bering-uClibc git repository== |
[path to git]/leaf/bering-uclibc# git tag -a -m "Release of LEAF Bering-uClibc 6.0.0-nn" v6.0.0-nn | [path to git]/leaf/bering-uclibc# git tag -a -m "Release of LEAF Bering-uClibc 6.0.0-nn" v6.0.0-nn | ||
Line 60: | Line 56: | ||
Change to the created folder and upload Readme and all the images. | Change to the created folder and upload Readme and all the images. | ||
+ | |||
+ | ==Commit Packages to SF SCM with release-to-git.sh== | ||
+ | tbd | ||
==Create Packages page== | ==Create Packages page== |
Revision as of 18:03, 24 August 2019
The Release Process | ||
---|---|---|
Prev | Bering-uClibc 6.x - Developer Guide |
Contents
- 1 Introduction
- 2 Rebuild new release from source
- 3 Sign packages with GPG maintainer key
- 4 Create images and source tarball
- 5 Tag release in LEAF Bering-uClibc git repository
- 6 Create README and Announcement
- 7 Upload files to SF FRS
- 8 Commit Packages to SF SCM with release-to-git.sh
- 9 Create Packages page
- 10 Wiki Changes
Introduction
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) administrator privileges.
Rebuild new release from source
It is recommended to do a completly fresh build from the sources. Use the command:
./buildtool distclean
Compile the build environment and all packages.
./tools/buildall.sh
To compile build environments and packages for all supported architectures in one go, the shell script build_all_archs.sh
has been added in the tools directory.
To save time, it is also possible to blacklist packages that are known not to build or only necessaryfor special tasks (e.g. valgrind.lrp<code>.
Sign packages with GPG maintainer key
tbd
Create images and source tarball
Create the images:
fakeroot ./buildimage.pl --kernel-arch geode --image-type syslinux --variant serial fakeroot ./buildimage.pl --kernel-arch i486 --image-type isolinux --variant vga fakeroot ./buildimage.pl --kernel-arch i486 --image-type syslinux --variant serial fakeroot ./buildimage.pl --kernel-arch i486 --image-type syslinux --variant vga fakeroot ./buildimage.pl --kernel-arch i686 --image-type syslinux --variant vga fakeroot ./buildimage.pl --kernel-arch i686 --image-type isolinux --variant vga ...
It is a good idea to finally test the newly build version with qemu:
qemu-system-i386 -enable-kvm -m 512 -cdrom image/Bering-uClibc_6.0.0-nn_i486_isolinux_vga.iso
Create the sources tarball as required by SF policy:
cd [path to git]bering-uclibc$ git archive --format=tgz -9 HEAD -o [your/upload-dir]/Bering-uClibc_6.0.0-nn_src.tgz
Tag release in LEAF Bering-uClibc git repository
[path to git]/leaf/bering-uclibc# git tag -a -m "Release of LEAF Bering-uClibc 6.0.0-nn" v6.0.0-nn [path to git]/leaf/bering-uclibc# git push origin v6.0.0-nn
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.
Commit Packages to SF SCM with release-to-git.sh
tbd
Create Packages page
Wiki Changes
Known Issues
Changelog
Prev | Up |