[Zaf-commit] SF.net SVN: zaf: [9133] trunk/locale/localedata/README

[<dwa...@us...>]

Revision: 9133
          http://zaf.svn.sourceforge.net/zaf/?rev=9133&view=rev
Author:   dwaynebailey
Date:     2007-04-20 01:00:45 -0700 (Fri, 20 Apr 2007)

Log Message:
-----------
Update README

Modified Paths:
--------------
    trunk/locale/localedata/README

Modified: trunk/locale/localedata/README
===================================================================
--- trunk/locale/localedata/README	2007-04-20 07:55:01 UTC (rev 9132)
+++ trunk/locale/localedata/README	2007-04-20 08:00:45 UTC (rev 9133)
@@ -1,22 +1,30 @@
+NOTE: These locales are for development and testing.  The locales you want are in glibc
+which should be part of your Linux distribution.
+
 Updateing locales:
+------------------
+You have some fixes that need to go into a locale:
 
-* Get the latest from CVS
+* Sync with the latest from CVS
   http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/localedata/locales/?cvsroot=glibc
-* Check changes between zaf and glibc CVS
-* Make updates
+* Update ChangeLog and checkin changes between zaf and glibc CVS
+* Make updates/corrections and checkin as needed
 * Test
 * Report bug with patch: http://sources.redhat.com/bugzilla/enter_bug.cgi
-* Do releasing
+* Release
 
-Release:
+Making/Tagging a new version:
+-----------------------------
 
 * Change version number and date
 * checkin and tag file: e.g. locale-ve_ZA-0_3
-* Create bug in glibc against localedata
+  svn copy en_ZA https://zaf.svn.sourceforge.net/svnroot/zaf/tags/locale-en_ZA-1_3_1
 
-Bundled release:
+Creating a release bundled:
 
 * Tag all files in the bundle: e.g. locale-ZA-0_3
+  svn copy localedata/ https://zaf.svn.sourceforge.net/svnroot/zaf/tags/locale-ZA-0_4 
 * Create tarball
+  tar cvjf locale-ZA-0.4.tar.bz2 localedata/
 * Upload to SF
 * Announce on FM


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.