You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2016/01/24 21:25:39 UTC

[jira] [Commented] (BIGTOP-1463) We need a better automation of the release process.

    [ https://issues.apache.org/jira/browse/BIGTOP-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114517#comment-15114517 ] 

Konstantin Boudnik commented on BIGTOP-1463:
--------------------------------------------

I've tried to play a bit with maven-release-plugin, but their data flow is somewhat different from ours, plus some of our submodules are detached (for a reason) from the top-level project. As the result, branching, version updates, etc. might be better just done manually for now. Hopefully, later we'll just move to gradle plugin and be done with it.

> We need a better automation of the release process.
> ---------------------------------------------------
>
>                 Key: BIGTOP-1463
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1463
>             Project: Bigtop
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.8.0
>            Reporter: Konstantin Boudnik
>            Priority: Blocker
>             Fix For: 1.2.0
>
>
> At the moment, the release process is driven by the wiki page https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
> The info is very helpful, but it needs to be updated and also requires a number of manual steps.
> Let's have a one-command release process that will include all needed steps like iTest, test artifacts uploads. as well as site creation and release artifacts deployment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)