Re-worked text in dev docs around JIRA issues.
Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/6bac504d Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/6bac504d Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/6bac504d Branch: refs/heads/TINKERPOP-1360 Commit: 6bac504d5be437bd79220ff2d96816200927c971 Parents: 8ebaf60 Author: Stephen Mallette <sp...@genoprime.com> Authored: Wed Jul 13 16:49:41 2016 -0400 Committer: Stephen Mallette <sp...@genoprime.com> Committed: Wed Jul 13 16:49:41 2016 -0400 ---------------------------------------------------------------------- docs/src/dev/developer/release.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/6bac504d/docs/src/dev/developer/release.asciidoc ---------------------------------------------------------------------- diff --git a/docs/src/dev/developer/release.asciidoc b/docs/src/dev/developer/release.asciidoc index 0190b0e..db936f3 100644 --- a/docs/src/dev/developer/release.asciidoc +++ b/docs/src/dev/developer/release.asciidoc @@ -54,9 +54,9 @@ during this period. .. Review JIRA tickets in the release and ensure that: ... All tickets categorized by having a "Component" assigned. ... All tickets are either of type "Bug" or "Enhancement". -... No tickets are marked as "Resolved" - convert these to "Closed". -... Close tickets where work was completed, but the ticket was left open (e.g. search for "closed the pull request" in -comments for hints on possible candidates). +... All tickets where work was completed are "Closed" +.... Search for "closed the pull request" in comments for hints on possible tickets that were left open by mistake). +.... Look for tickets marked as "Resolved" (some users might not have rights to mark as "Closed" - convert these to "Closed". . When all documentation changes are in place, use `bin/publish-docs.sh` to deploy a final `SNAPSHOT` representation of the docs and thus validate that there are no issues with the documentation generation process. Request review of the published documentation on the dev mailing list.
