You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Elek, Marton (JIRA)" <ji...@apache.org> on 2017/03/08 19:36:38 UTC

[jira] [Created] (HADOOP-14162) Improve release scripts to automate missing steps

Elek, Marton created HADOOP-14162:
-------------------------------------

             Summary: Improve release scripts to automate missing steps
                 Key: HADOOP-14162
                 URL: https://issues.apache.org/jira/browse/HADOOP-14162
             Project: Hadoop Common
          Issue Type: Improvement
          Components: build
            Reporter: Elek, Marton
            Assignee: Elek, Marton


According to the conversation on the dev mailing list one pain point of the release making is that even with the latest create-release script a lot of steps are not automated.

This Jira is about creating a script which guides the release manager throw the proces:

Goals:
  * It would work even without the apache infrastructure: with custom configuration (forked repositories/alternative nexus), it would be possible to test the scripts even by a non-commiter.  
  * every step which could be automated should be scripted (create git branches, build,...). if something could be not automated there an explanation could be printed out, and wait for confirmation
  * Before dangerous steps (eg. bulk jira update) we can ask for confirmation and explain the 
  * The run should be idempontent (and there should be an option to continue the release from any steps).  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org