From 45684b205b86c0423efff67f28f7e8fc1f02561f Mon Sep 17 00:00:00 2001
From: Chris Burgess <chris@giantrobot.co.nz>
Date: Mon, 4 Sep 2017 10:42:22 +1200
Subject: [PATCH] Improve docs for publishing an extension.
Previously it read that you only needed to create a release on *subsequent* releases, but my experience was that the extension was not available until the initial release was made also. Rewrote to clarify this.
Also made a few additions to inline docs on the create a release node page. These can be recorded over in CiviCRM.org website repo via Features.
Refs #323.
---
docs/extensions/publish.md | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/docs/extensions/publish.md b/docs/extensions/publish.md
index 9a1266c4..d11ed4f1 100644
--- a/docs/extensions/publish.md
+++ b/docs/extensions/publish.md
@@ -54,11 +54,12 @@ detected, published, and submitted for translation.
message, you'll need to email [info@civicrm.org](mailto:info@civicrm.org)
with your user id and request permission to publish extensions.
- Fill out all required fields. Also provide the "Git URL" for the extension.
+- Complete the steps in "Publishing an extension release" below.
- Within a day, you will receive an email notifying you that the extension
was published on civicrm.org or that a problem with the extension manifest
(`info.xml`) prevented publication.
-### Publishing subsequent releases:
+### Publishing an extension release:
- Update the extension manifest and push the changes to your GitHub repository.
At minimum you'll need to increment the version number.
@@ -67,6 +68,8 @@ detected, published, and submitted for translation.
git tag -a v1.2.0
git push origin v1.2.0
+- Visit your extension node (created in "Publishing an extension" step above)
+ and click "Add CiviCRM-native release" at bottom of page.
- Within a day, you will receive an email notifying you that the release
was published on civicrm.org or that a problem with the extension manifest
prevented publication.
--
GitLab