Difference between revisions of "Bering-uClibc 6.x - Developer Guide - The Release Process"

From bering-uClibc
Jump to: navigation, search
(Upload files to SF FRS)
(Create README and Announcement)
Line 48: Line 48:
 
  [path to git]/leaf/bering-uclibc# git push origin v6.0.0-nn
 
  [path to git]/leaf/bering-uclibc# git push origin v6.0.0-nn
  
==Create README and Announcement==
+
==Create README (and Announcement)==
 +
This should be obvious.
 +
Announcements are not made on a regular basis though.
 +
 
 
==Upload files to SF FRS==
 
==Upload files to SF FRS==
  

Revision as of 18:14, 24 August 2019

The Release Process
Prev Bering-uClibc 6.x - Developer Guide

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)

This should be obvious. Announcements are not made on a regular basis though.

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, the Images and the source tarball.

Commit Packages to SF SCM with release-to-git.sh

tbd


Prev Up