[jira] [Commented] (TINKERPOP-1383) publish-docs.sh might publish to current too early

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455762#comment-15455762
 ] 

ASF GitHub Bot commented on TINKERPOP-1383:
---

Github user dkuppitz commented on the issue:

https://github.com/apache/tinkerpop/pull/396
  
CTR'ed.


> 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)

[jira] [Commented] (TINKERPOP-1383) publish-docs.sh might publish to current too early

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15455761#comment-15455761
 ] 

ASF GitHub Bot commented on TINKERPOP-1383:
---

Github user asfgit closed the pull request at:

https://github.com/apache/tinkerpop/pull/396


> 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)

[jira] [Commented] (TINKERPOP-1383) publish-docs.sh might publish to current too early

[stephen mallette (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15388427#comment-15388427
 ] 

stephen mallette commented on TINKERPOP-1383:
-

+1

> 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.1.4, 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)