[postgis-tickets] [SCM] PostGIS branch stable-2.4 updated. 63c987e448bf8f028d9738df1ee7ba14eaa18b03

git at osgeo.org git at osgeo.org
Fri Aug 14 18:51:52 PDT 2020


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 "PostGIS".

The branch, stable-2.4 has been updated
       via  63c987e448bf8f028d9738df1ee7ba14eaa18b03 (commit)
      from  1129a184a5b03fb79353e8a32a9f2b4246c71018 (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 63c987e448bf8f028d9738df1ee7ba14eaa18b03
Author: Regina Obe <lr at pcorp.us>
Date:   Fri Aug 14 21:51:28 2020 -0400

    how to release and version info

diff --git a/HOWTO_RELEASE b/HOWTO_RELEASE
index f377810..9f5c076 100644
--- a/HOWTO_RELEASE
+++ b/HOWTO_RELEASE
@@ -1,6 +1,6 @@
 How to release
 ~~~~~~~~~~~~~~
-Date: 2018-04-01
+Date: 2020-08-14
 
 Versioning Scheme
 -----------------
@@ -57,9 +57,14 @@ documentation -- that means having the required software:
 Release procedure
 -----------------
 
-- Re-generate the ChangeLog (make ChangeLog)
+- For first micro of a minor, make sure to pull the latest translations from transifex
+   TODO: more detail here - there is a job on debbie for 3.1 for examples
+   https://debbie.postgis.net/view/PostGIS/job/PostGIS_docs_translations_2.5
+   and she's setup with an api key to pull and push translations.
+
+- Ensure all bots are green: https://trac.osgeo.org/postgis
 - Edit NEWS: set release date and check all notable changes have
-  been reported (extract from ChangeLog).
+  been reported (extract from git log).
 - Edit README.postgis and set release date and version.
 - Add release notes in doc/release_notes.xml
 - Update Version.config to drop the "dev" suffix
@@ -69,33 +74,31 @@ Release procedure
 	(this should only be needed for trunk release)
 - Commit all changes
 - If this is a minor or major release (no branch exists):
-	   $ base=http://svn.osgeo.org/postgis/
 	   $ rev=x.x
-	   $ svn copy -m "Branch $rev" $base/trunk $base/branches/$rev
+	   $ git checkout master; git checkout -b "$rev"; git push -u osgeo $rev
 
 	   Go to: https://debbie.postgis.net and copy last branch version and make new job
 	   a) Replace PostGIS_* string params with new version
 	   b) Replace repository url with new branch repo url
 	   c) Update the PostGIS_trunk by updating the PostGIS_* string params
 
-	   Go to: ​https://trac.osgeo.org/postgis/ edit the matrix to reflect new branch
+	   Go to: https://trac.osgeo.org/postgis/ edit the matrix to reflect new branch
 
 - Tag branch:  (replace x.x and x.x.x with minor and micro version e.g 2.3, 2.3.1
-   $ base=http://svn.osgeo.org/postgis/
-   $ brev=x.x
    $ rev=x.x.x
-   $ svn copy -m "Tagged release $rev" $base/branches/$brev $base/tags/$rev
+   $ git tag -a $rev -m "Tagged release $rev"; git push osgeo --tags
 - Run: sh make_dist.sh $rev (note, debbie should have already done this,
       and the file will be waiting in postgis.net/stuff.  You might need to wait a few minutes to see it.)
       If impatient check status of job - https://debbie.postgis.net/job/PostGIS_Make_Dist/
 - Documentation should also have been built and should be in postgis.net/stuff
   (this sometimes takes sometime so wait 15 minutes)
 - Test generated tarball (including extension upgrade)
-- Copy tarball, pdf, doc-html.. to http://download.osgeo.org/postgis/ web site and edit postgis.net/source page
+- Copy tarball, pdf, doc-html.. to https://download.osgeo.org/postgis/ web site and edit postgis.net/source page
 - Announce on e-mail
     - postgis-users
     - postgis-devel
-    - pgsql-announce (send note to david at fetter dot org to be included in Weekly news)
+    - pgsql-announce (send email just to them, not with other ccs, they reject if others in cc)
+    - send note to david at fetter dot org to be included in Weekly news
     - osgeo-discuss
 - Update web sites
     - PostGIS News
@@ -104,10 +107,13 @@ Release procedure
        b) Update links on https://git.osgeo.org/gitea/postgis/postgis.net/src/master/_content/pages/source.html
        c) commit and wait 5 minutes to see changes on website
     - PostGIS doc release versioned doc - http://postgis.net/documentation/
+    - On postgis.net server, change /etc/nginx/sites-enabled/postgis.net (Versionless URL line )
+         - nginx -t #to confirm you didn't breat the config
+         - service nginx reload
      Verify the documentation is up to date (might need to change the apach config)
     - Wikipedia
     - Twitter
-       This should automatically happen as a result of posting to PostGIS website since Planet PostGIS autotweets.
+       This should automatically happen as a result of posting to PostGIS website since Planet PostGIS and Planet PostgreSQL both autotweet.
 - Update Trac and make old Milestone as completed
 - Push the revision number forward (see Versioning Scheme)
 - Remove the "dev" suffixed version from extensions/upgradeable_versions.mk
diff --git a/README.postgis b/README.postgis
index a299d3e..765c583 100644
--- a/README.postgis
+++ b/README.postgis
@@ -1,9 +1,9 @@
 PostGIS - Geographic Information Systems Extensions to PostgreSQL
 =================================================================
 
-:Version: 2.4.7
-:Date: 2019-03-11
-:Website: http://postgis.net
+:Version: 2.4.9
+:Date: 2020-08-14
+:Website: https://postgis.net
 
 This distribution contains a module which implements GIS simple features, ties
 the features to R-tree indexing, and provides many spatial functions for

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

Summary of changes:
 HOWTO_RELEASE  | 30 ++++++++++++++++++------------
 README.postgis |  6 +++---
 2 files changed, 21 insertions(+), 15 deletions(-)


hooks/post-receive
-- 
PostGIS


More information about the postgis-tickets mailing list