You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Daniel Kuppitz (JIRA)" <ji...@apache.org> on 2016/09/01 15:27:20 UTC

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

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

Daniel Kuppitz closed TINKERPOP-1383.
-------------------------------------

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