[dia] Updated INSTALL, RELEASE-PROCESS and MAINTAINERS

[Hans Breuer <hans src gnome org>]

commit ff5ed9842e9cfc4803a10c86ccc6ec4758f13e4e
Author: Hans Breuer <hans breuer org>
Date:   Fri Apr 17 11:38:39 2009 +0200

    Updated INSTALL, RELEASE-PROCESS and MAINTAINERS
    
    Translated from SVN usage to Git, some spelling corrections
---
 INSTALL         |   19 ++++++++++---------
 MAINTAINERS     |    8 ++++----
 RELEASE-PROCESS |   22 ++++++++++------------
 3 files changed, 24 insertions(+), 25 deletions(-)

diff --git a/INSTALL b/INSTALL
index 4b22f2c..31896bf 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,8 +1,8 @@
 NOTE FOR WINDOWS USERS:
 =======================
 
-If you're reading this and just want to use Dia rather than
-compiling/extending it, you're in the wrong place.  Please go to
+If you are reading this and just want to use Dia rather than
+compiling/extending it, you are in the wrong place.  Please go to
 http://dia-installer.sourceforge.net and download the precompiled, easily
 installable binary.
 
@@ -44,7 +44,7 @@ also required for Gtk.  It can be found here:
 
 A full list of packages required for building Dia in the order in which
 they should be installed.  Note that if the versions here are just the
-minimum required by Dia, if you plan to use a newer GTK+, you'll need a
+minimum required by Dia, if you plan to use a newer GTK+, you will need a
 newer GLib and ATK at the least.  When possible, use the newest stable
 release. 
 
@@ -65,12 +65,11 @@ Cairo is used for anti-alised rendering to screen or PNG as well as PDF:
   Minimum version required (if at all) is 1.2
 Libart allows anti-aliased rendering and anti-aliased export to PNG:
   http://www.artofcode.com/libart.html
-Libpng is need for anti-aliased PNG export:
+Libpng is need for libart based anti-aliased PNG export:
   http://download.sourceforge.net/libpng/
 Libxslt allows export through XSLT translation schemas:
   ftp://ftp.gnome.org/pub/GNOME/sources/libxslt/
-Extra Gnome support (limited) is available with installation of the gnome
-  libs:
+Extra Gnome support (limited) is available with installation of the gnome libs:
   ftp://ftp.gnome.org/pub/GNOME/sources/gnome-libs/
   Note that ./configure must be run with --enable-gnome to use Gnome.
 Python scripting is possible by adding --with-python and having the
@@ -110,16 +109,18 @@ AFS
           until ln "$srcfile" "$lockfile" 2>/dev/null; do
 
 Solaris
-	The gettext that comes with Solaris doesn't define
+	The gettext that comes with Solaris does not define
 	bind_textdomain_codeset.  Use the gettext and libiconv from
 	ftp.gnu.org instead.
 
-COMPILING FROM SVN:
+COMPILING FROM GIT:
 ===================
 
-If you are using the SVN version of Dia you need to have the following programs:
+If you are using the Git version of Dia you need to have the following programs:
 automake 1.4, autoconf 2.50, libtool 1.3, GNU gettext 0.10.38, intltool 0.21
 
+Get it by: git clone git://git.gnome.org/dia
+
 Then run ./autogen.sh instead of configure to create all needed files.
 
 WARNING: if you run ./autogen.sh, you will need to have gettext
diff --git a/MAINTAINERS b/MAINTAINERS
index 4b2fef8..e75994e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1,15 +1,15 @@
 These are the *current* maintainers of Dia:
 
-Lars Clausen
-E-mail: lars raeder dk
-Userid: lclausen
-
 Hans Breuer
 E-mail: hans breuer org
 Userid: hans
 
 These are the previous maintainers of Dia:
 
+Lars Clausen
+E-mail: lars raeder dk
+Userid: lclausen
+
 Name: Cyrille Chepelov
 Email: cyrille chepelov org
 
diff --git a/RELEASE-PROCESS b/RELEASE-PROCESS
index 4dce5c7..d19721a 100644
--- a/RELEASE-PROCESS
+++ b/RELEASE-PROCESS
@@ -16,7 +16,7 @@ Contents
 When a new version is about to be released:
 
 0) Day Zero (D+0): The core developers announce their intention of
-   making a new release. They call for a feature freeze on the SVN
+   making a new release. They call for a feature freeze on the Git
    HEAD (bug fixes are okay to commit). They also announce the
    provisional duration of the freeze before the first release
    candidate tarball is about to be made (actual freeze duration may vary for
@@ -24,7 +24,7 @@ When a new version is about to be released:
    last release; for the purpose of this document, it's assumed to be
    three days).
 
-   Advanced users are encouraged to download the SVN HEAD or the
+   Advanced users are encouraged to download the 'git master' or the
    snapshot tarballs, and pound on them.
 
    Make sure to check for open Bugzilla bugs with the PATCH keyword.
@@ -38,10 +38,9 @@ When a new version is about to be released:
    to be updated.
 
 2) D+3: a release candidate tarball is made. It is called
-   $VERSION-pre1. Simultaneously, a SVN "tag" is created with the name
+   $VERSION-pre1. Simultaneously, a tag is created with the name
    "DIA_$VERSION_RELEASE" (with the non-alphanumeric characters in $VERSION
-   replaced by underscores, e.g.: svn copy svn+ssh://hans svn gnome org/svn/dia/trunk \
-   svn+ssh://hans svn gnome org/svn/dia/tags/DIA_0_97_PRE1).
+   replaced by underscores, e.g.: git tag -a DIA_0_97_PRE3).
    $VERSION-pre1 is registered with the Bugzilla, however it is encouraged
    that bug reports are made directly (or simultaneously) to the mailing
    list.
@@ -63,15 +62,14 @@ When a new version is about to be released:
    (cvs update -j).
 
 3b) D+10: if there are no release-critical bugs in the pre-release,
-   then the same source (fetched from the SVN branch) is rebuilt with the
+   then the same source (fetched from the Git branch) is rebuilt with the
    final $VERSION number (and the resulting "new" version is re-tagged
-   in SVN). $VERSION is registered with the Bugzilla, and all
+   in Git). $VERSION is registered with the Bugzilla, and all
    $VERSION-preX are removed (from now on, bugs against -preX are
    rejected as INVALID).
-   A real SVN branch is created with the name "dia-$VERSION" with the 
+   A Git branch is created with the name "dia-$VERSION" with the 
    non-alphanumeric characters in $VERSION replaced by dashes, e.g.: 
-   svn copy svn+ssh://hans svn gnome org/svn/dia/trunk \
-   svn+ssh://hans svn gnome org/svn/dia/branches/dia-0-97).
+   git checkout -b dia-0-97 && git push dia-0-97
 
 4) once the new release is complete and uploaded, announcements on
    freshmeat, the dia web site, the dia mailing list,
@@ -80,11 +78,11 @@ When a new version is about to be released:
    various distributions is also a good idea, get names from MAINTAINERS
    and update those who have changed.
 
-5) the SVN HEAD freeze is lifted one week /after/ the release is
+5) the Git HEAD freeze is lifted one week /after/ the release is
    generally available, unless a release critical bug is discovered in
    the release. If the latter is the case, a new, fixed "brown bag" release is
    released and announced as soon as possible (extending the one-week
-   delay on the SVN HEAD thaw).
+   delay on the Git HEAD thaw).
 
    Once the head is lifted, the release branch is considered dead and
    should no longer be used.