[geos-commits] [SCM] GEOS branch master updated. ce5a7248a1eda88c33d0e7ab50c37efd6b1570de

git at osgeo.org git at osgeo.org
Fri Sep 27 15:48:31 PDT 2019


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GEOS".

The branch, master has been updated
       via  ce5a7248a1eda88c33d0e7ab50c37efd6b1570de (commit)
      from  d48dbefd0079da341cc5fb5f27a652858622d256 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit ce5a7248a1eda88c33d0e7ab50c37efd6b1570de
Author: Paul Ramsey <pramsey at cleverelephant.ca>
Date:   Fri Sep 27 15:48:20 2019 -0700

    Reorganize release directions

diff --git a/HOWTO_RELEASE b/HOWTO_RELEASE
index 6c1a477..a94f044 100644
--- a/HOWTO_RELEASE
+++ b/HOWTO_RELEASE
@@ -1,49 +1,44 @@
-1. Verify that the versions currently set (see 10 and 11 below) make
+1. Verify that the versions currently set in Version.txt
    sense for this release.
 
+    - GEOS_VERSION_PATCH
+    - GEOS_VERSION_MINOR
+    - GEOS_VERSION_MAJOR
+
+    - CAPI_INTERFACE_CURRENT
+    - CAPI_INTERFACE_REVISION
+    - CAPI_INTERFACE_AGE
+
+    Always increase the revision value.
+    Increase the current value whenever an interface has been added, removed or changed.
+    Increase the age value only if the changes made to the ABI are backward compatible.
+
 2. Run 'make distcheck', fix any problem with it.
 
 3. Update the NEWS file (extract most important things from the
-   repository log). Make sure to update the release date
+   repository log). Make sure to update the release date.
 
 4. Commit the changes in the NEWS file.
 
 5. Tag the release:
+
    $ git tag MAJOR.MINOR.PATCH
+   $ git push --follow-tags
 
 6. Run 'make dist-bzip2'.
+
    $ ./autogen.sh && ./configure && make dist-bzip2
 
-7. Verify that you can unpack and build the tarball
+7. Verify that you can un-pack and build the tarball.
 
 8. Copy the tarball to upload.osgeo.org:/osgeo/download/geos
 
-9. Increment all the version numbers for the next release, as below.
-
-10. Increment CAPI_INTERFACE_X in configure.ac
-    - For a release with no interface changes just bump REVISION.
-      [ Even if *nothing* changed in CAPI ]
-    - Adding interfaces, bump CURRENT/AGE, set REVISION to 0.
-    - Deleting interfaces / compatibility issues - bump CURRENT, others to zero
-      [ THIS MUST BE CAREFULLY AVOIDED ]
-
-11. Increment release versions in Version.txt
-
-      - GEOS_VERSION_PATCH
-      - GEOS_VERSION_MINOR
-      - GEOS_VERSION_MAJOR
-
-      - CAPI_INTERFACE_CURRENT
-      - CAPI_INTERFACE_REVISION
-      - CAPI_INTERFACE_AGE
+9. Increment all the version numbers for the next release (described in 1 above).
 
-      Always increase the revision value.
-      Increase the current value whenever an interface has been added, removed or changed.
-      Increase the age value only if the changes made to the ABI are backward compatible.
+10. Update wiki page https://trac.osgeo.org/geos/ at Download section
 
-12. Update wiki page https://trac.osgeo.org/geos/ at Download section
     - Add latest release
     - Remove previos patch level release (if any)
 
-13. Announce
+11. Announce on geos-devel
 

-----------------------------------------------------------------------

Summary of changes:
 HOWTO_RELEASE | 47 +++++++++++++++++++++--------------------------
 1 file changed, 21 insertions(+), 26 deletions(-)


hooks/post-receive
-- 
GEOS


More information about the geos-commits mailing list