[Uim] Release manual draft

[Jeroen Ruigrok/asmodai]

-On [20050614 04:04], TOKUNAGA Hiroyuki (tkng at xem.jp) wrote:
>This is a draft of release manual. If there's no comment, I'll commit
>this manual tommorow. (Though it's a very rough, incomplete manual,
>would be better than nothing.)

And now with attachment (note to self: attachment is a, not q).

-- 
Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
Free Tibet! http://www.savetibet.org/ | http://ashemedai.deviantart.com/
http://www.tendra.org/   | http://www.in-nomine.org/
Unto the pure all things are pure...
-------------- next part --------------
Release manual for uim
======================

As of this moment, uim has three types of release of the same version.  They
are alpha, beta and final. Alpha may be an unstable release and it may be
untested. After the alpha release, any new big features may not be committed.

The beta release must be tested partially by the maintainer. In the ideal case
it will be well-tested by the maintainer. If a first beta (beta1) is too
unstable, a second beta (beta2) should be released to ensure the quality of
the final release. After beta release, new features may not be committed.

The final release is really the final release. It must be tested well.

For each release the following steps should be followed. To make the final
release, you have to repeat the following procedure at least three times.

1. Declare 'I will make a new release' to the mailing list.

   Committers must not add a new unstable feature if a new release has been
   announced.

2. Gather up details of the release from each committer.

   The ChangeLog of uim is very long, so making a release note from the
   ChangeLog is hard work. Therefore a committer should send details of their
   commit. Maybe we sould prepare a better way.

3. Checkout a fresh version from svn.

   svn co svn+ssh://freedesktop.org/srv/uim.freedesktop.org/svn/trunk

4. Do a build test with make releasetest

   This test is not enough, but worth doing. It is especially useful when a
   new file is added. As a TODO, we should do unit testing at this point.

5. Do test

   This item needs many many description... I must fill this item later.

6. Increment the version number in configure.ac and Project-Id-Version in
   po/*.po, then commit it.

7. make dist

8. Copy the source tarball to http://uim.freedesktop.org/releases

9. Tag to tags/uim-x.y.z

   svn copy svn+ssh://freedesktop.org/srv/uim.freedesktop.org/svn/trunk\
   svn+ssh://freedesktop.org/srv/uim.freedesktop.org/svn/tags/uim-x.y.z

10. Send a message to uim at freedesktop.org.

11. Update the web page.