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

From bering-uClibc
Jump to: navigation, search
m
(Rebuild new release from source)
Line 13: Line 13:
  
 
== Rebuild new release from source==
 
== 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
  
 
==Clean up Trac==
 
==Clean up Trac==

Revision as of 16:56, 7 March 2011

The Release Process
Prev Bering-uClibc 4.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) 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

Clean up Trac

Edit the milestone in LEAF Trac and either close the active tickets or move them to later version.

Create images and source tarball

Tag release in SCM

Create README and Announcement

Upload files to SF FRS

Commit Packages to SF SCM

Create Packages page

Wiki Changes

Known Issues

Changelog


Prev Up