[uim-commit] r912 - trunk

[tkng at freedesktop.org]

Author: tkng
Date: 2005-06-27 04:04:29 -0700 (Mon, 27 Jun 2005)
New Revision: 912

Modified:
   trunk/RELEASING
Log:
* RELEASING: Some sentences were corrected. Thanks to Jeroen Ruigrok/asmodai.


Modified: trunk/RELEASING
===================================================================
--- trunk/RELEASING	2005-06-27 09:26:15 UTC (rev 911)
+++ trunk/RELEASING	2005-06-27 11:04:29 UTC (rev 912)
@@ -1,46 +1,46 @@
 Release manual for uim
 ======================
 
-As of this moment, uim have three types of release on the same version.
-They are alpha, beta and final. Alpha may be unstable release, may be
-untested. After alpha release, new big features must not be committed.
+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.
 
-Beta release must tested partially by the maintainer. Ideally well
-tested by the maintainer. If beta1 is too unstable, beta2 should be
-release to ensure the quality of final release. After beta release, new
-features must 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.
 
-Final release is really final release. Must be tested well.
+The final release is really the final release. It must be tested well.
 
-In each release, following steps should be filled. To make final
-release, you have to repeat following procedure at least three times.
+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.
 
-1. Declare 'I will make new release' to the mailing list.
+   Committers must not add a new unstable feature if a new release has been
+   announced.
 
-Committers must not add a new unstable feature if the declaration came.
+2. Gather up details of the release from each committer.
 
-2. Gather up brief of the release from each committers.
+   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.
 
-ChangeLog of uim is very long, so making release note from the ChangeLog
-is a hard work. Therefore committer should send brief of their commit. Maybe
-we sould prepare better way.
+3. Checkout a fresh version from svn.
 
-3. Checkout fresh version from svn.
+   svn co svn+ssh://freedesktop.org/srv/uim.freedesktop.org/svn/trunk
 
- svn co svn+ssh://freedesktop.org/srv/uim.freedesktop.org/svn/trunk
+4. Do a build test with make releasetest
 
-4. Do 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.
 
-   This test is not enough, but worth. Especially it's useful when a
-   new file is added. As a TODO, we should do unit test at this point.
-
 5. Do test
 
-   This item needs many many description... I must fill this item
-   later.
+   This item needs many many description... I must fill this item later.
 
-6. Increment the version in configure.ac, then commit it.
+6. Increment the version number in configure.ac and Project-Id-Version in
+   po/*.po, then commit it.
 
 7. make dist
 
@@ -48,9 +48,10 @@
 
 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
+   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 web page.
+11. Update the web page.
+