[
https://issues.apache.org/jira/browse/TINKERPOP-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455729#comment-15455729
]
ASF GitHub Bot commented on TINKERPOP-1383:
-------------------------------------------
GitHub user dkuppitz opened a pull request:
https://github.com/apache/tinkerpop/pull/396
TINKERPOP-1383 publish-docs.sh might publish to current too early
Added a separate script to update the "current" docs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/tinkerpop TINKERPOP-1383
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/396.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #396
----
commit 7279689db5d38aaaf796192ac165fd099fc38515
Author: Daniel Kuppitz <[email protected]>
Date: 2016-09-01T15:09:06Z
Added a separate script to update the "current" docs.
----
> publish-docs.sh might publish to current too early
> --------------------------------------------------
>
> Key: TINKERPOP-1383
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1383
> Project: TinkerPop
> Issue Type: Bug
> Components: build-release
> Affects Versions: 3.1.3
> Reporter: stephen mallette
> Assignee: Daniel Kuppitz
> Fix For: 3.2.2
>
>
> In the standard release flow of things, the release manager runs
> `bin/publish-docs.sh` right before VOTE which means that `/current` gets
> updated at least 3 days before we announce the release.
> Maybe updating current should be a specific command?
> {code}
> bin/publish-docs.sh --update userName
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
