[postgis-tickets] [SCM] PostGIS branch stable-3.0 updated. 3f21bfb473f63510f6ff0e8c00b4b1f78cafee5a

[git at osgeo.org]

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-3.0 has been updated
       via  3f21bfb473f63510f6ff0e8c00b4b1f78cafee5a (commit)
       via  bd9009f18b13c103f08aad91bbf781c091b248d7 (commit)
      from  85fd73f570544e6ea9f62b08bc46214aff018ee1 (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 3f21bfb473f63510f6ff0e8c00b4b1f78cafee5a
Merge: bd9009f 85fd73f
Author: Regina Obe <lr at pcorp.us>
Date:   Mon Feb 3 03:53:13 2020 -0500

    Merge branch 'stable-3.0' of https://git.osgeo.org/gitea/postgis/postgis into stable-3.0


commit bd9009f18b13c103f08aad91bbf781c091b248d7
Author: Regina Obe <lr at pcorp.us>
Date:   Mon Feb 3 03:53:03 2020 -0500

    Update how to release to use git instead of svn

diff --git a/HOWTO_RELEASE b/HOWTO_RELEASE
index bab5bb8..d5e5afe 100644
--- a/HOWTO_RELEASE
+++ b/HOWTO_RELEASE
@@ -1,6 +1,6 @@
 How to release
 ~~~~~~~~~~~~~~
-Date: 2019-10-19
+Date: 2020-02-02
 
 Versioning Scheme
 -----------------
@@ -58,14 +58,13 @@ Release procedure
 -----------------
 
 - 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.0 for examples 
-   https://debbie.postgis.net/view/PostGIS/job/PostGIS_docs_translations_3.0 
+   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_3.0
    and she's setup with an api key to pull and push translations.
-   
+
 - Ensure all bots are green: https://trac.osgeo.org/postgis
-- Re-generate the ChangeLog (make ChangeLog)
 - 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
@@ -75,29 +74,26 @@ 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=https://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=https://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 https://download.osgeo.org/postgis/ web site and edit postgis.net/source page and config.yaml 
+- 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
@@ -111,11 +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.conf (Versionless URL lines #current docs, #dev docs )
+    - 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

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

Summary of changes:
 HOWTO_RELEASE | 28 +++++++++++++---------------
 1 file changed, 13 insertions(+), 15 deletions(-)


hooks/post-receive
-- 
PostGIS