RFC Openmoko Distribution and Software release process
zecke at openmoko.org
Fri Jul 18 22:02:16 CEST 2008
we want to do our "first" release of a distribution and also have some stuff
created by Openmoko that currently only sits in SCM systems. So I started a
page in the wiki that could be our ReleasePolicy it is inspired by a small
howto from KDE .
For our software, we have quite some 1.0 (or 0.9) releases to make. These
include opkg (thanks to thos working on it), splinter, assassin, illume, our
flavor of Qtopia, ompower... so we should at least:
- Create branches and tags
- Update versions in the bugtracker and source
- Put tarballs somewhere
For our distro we have two requirements:
- Change the DISTRO_TYPE to release... otherwise we continue to allow
password less root login (nice for development, bad for a product)
- Change version of the distro
- Make backup of the build machine
- Provide sourcecode for license compliance and joy of users.
so please propose changes for the ReleasePolicy, whoever needs to do releases
should follow and extend/fix the policy. Again it is really important to set
the DISTRO_TYPE :)
PS: Looks like Julian will do the distro release?
More information about the devel