[postgis-tickets] [SCM] PostGIS; Spatial objects for PostgreSQL. branch master created. 54399b9f6b0f02e8db9444f9f042b8d4ca6d4fa4
git at osgeo.org
git at osgeo.org
Sun Oct 27 12:11:09 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 "PostGIS; Spatial objects for PostgreSQL.".
The branch, master has been created
at 54399b9f6b0f02e8db9444f9f042b8d4ca6d4fa4 (commit)
- Log -----------------------------------------------------------------
commit 54399b9f6b0f02e8db9444f9f042b8d4ca6d4fa4
Author: Sandro Santilli <strk at kbt.io>
Date: Sun Oct 27 20:10:39 2019 +0100
Tweak HOWTO_RELEASE
diff --git a/HOWTO_RELEASE b/HOWTO_RELEASE
index 25d5d27..dd4c8de 100644
--- a/HOWTO_RELEASE
+++ b/HOWTO_RELEASE
@@ -58,10 +58,10 @@ 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.0 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
@@ -75,9 +75,8 @@ 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
@@ -87,10 +86,8 @@ Release procedure
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 -am "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/
-----------------------------------------------------------------------
hooks/post-receive
--
PostGIS; Spatial objects for PostgreSQL.
More information about the postgis-tickets
mailing list