You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@thrift.apache.org by jk...@apache.org on 2018/09/17 10:38:50 UTC

svn commit: r1841060 - /thrift/cms-site/trunk/content/docs/committers/HowToPublish.md

Author: jking
Date: Mon Sep 17 10:38:50 2018
New Revision: 1841060

URL: http://svn.apache.org/viewvc?rev=1841060&view=rev
Log:
Update tagging procedure for release.

Modified:
    thrift/cms-site/trunk/content/docs/committers/HowToPublish.md

Modified: thrift/cms-site/trunk/content/docs/committers/HowToPublish.md
URL: http://svn.apache.org/viewvc/thrift/cms-site/trunk/content/docs/committers/HowToPublish.md?rev=1841060&r1=1841059&r2=1841060&view=diff
==============================================================================
--- thrift/cms-site/trunk/content/docs/committers/HowToPublish.md (original)
+++ thrift/cms-site/trunk/content/docs/committers/HowToPublish.md Mon Sep 17 10:38:50 2018
@@ -6,9 +6,10 @@ kind: doc
 1. ssh people.apache.org and set ''umask 0002''
 1. Copy the tarball, signature, and hashes to the official artifact rep:
 	1. mkdir -p /www/www.apache.org/dist/thrift/<version>
-		1. copy the tarball, signature, and checksums into the above dir
-1. Create a tag from your version branch:
-	1. svn cp .../thrift/branches/<version> .../thrift/tags/thrift-<version>
+	2. copy the tarball, signature, and checksums into the above dir
+1. Create a tag from your version branch.  We are using SemVer style tags starting with v0.12.0 to comply with dlang dub repository requirements.  SemVer is a well-known and widely accepted version format.
+	1. `git tag v0.xx.0`
+	1. `git push origin v0.xx.0`
 1. Update the website to point to the new version
 	1. edit /www/thrift.apache.org/thrift/download/index.html to point to the new release. See the [website documentation](/docs/committers/HowToThriftWebsite) for more details
-1. "Release" the version in JIRA and create the next version label and transition any tickets to the new version.
+1. "Release" the version in JIRA and create the next version label and transition any tickets to the new version.
\ No newline at end of file