reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1128) Speed up release process
Date Thu, 14 Jan 2016 21:33:39 GMT

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

Markus Weimer commented on REEF-1128:
-------------------------------------

+1 on speeding up the release process.

if we want to completely automate this, we will have to be able to build REEF.NET from a script.
It would be reasonable to also run the tests at that time, just like {{mvn release}} does.
What I am getting at: Is the speedup of our release process blocked by [REEF-729]?

> Speed up release process
> ------------------------
>
>                 Key: REEF-1128
>                 URL: https://issues.apache.org/jira/browse/REEF-1128
>             Project: REEF
>          Issue Type: Improvement
>          Components: Build infrastructure
>            Reporter: Mariia Mykhailova
>
> REEF-498 improved release manager's life a lot, but there is still room for improvement.
Let's think what else we can do to make the process faster.
> * Automate website update.
> This involves a change similar to https://github.com/apache/reef/pull/593, which can
be automated using new release version and its SHA512 as input (release date can be assumed
to be current date).
> * Automate step 3 of https://cwiki.apache.org/confluence/display/REEF/Release+Manager+Guide
> It requires several actions - create branch, run python script, commit the result, tag
it - which follow predefined pattern and can be done by a script.
> Any other suggestions?
> We could draft these scripts before 0.14 release, and merge them after 0.14 once they
are tested on a release.



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

Mime
View raw message