tinkerpop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stephen mallette (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TINKERPOP-1383) publish-docs.sh might publish to current too early
Date Thu, 21 Jul 2016 18:30:21 GMT

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

stephen mallette updated TINKERPOP-1383:
----------------------------------------
    Summary: publish-docs.sh might publish to current too early  (was: publish-docs.sh might
publish to current to early)

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

Mime
View raw message