[
https://issues.apache.org/jira/browse/HADOOP-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923878#comment-15923878
]
Elek, Marton commented on HADOOP-14162:
---------------------------------------
@aw I understand your concern that a customizable create-release script could
allow to create custom (non repeatable) release build (but anyway it could be
possible even with the current script. There is no guarantees if anybody didn't
modify the jars after/during the process).
But what is your suggestion? Is it acceptable if there would be no step flag?
I think the separation of the steps to different files:
* could help to understand the process itself.
* could help to me to backport the selected tasks to older branches (may be
not all of them will be valid for an older version)
So what about to separate the steps, but _don't_ allow to run a selected step
or continue from a specific step?
> 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: [email protected]
For additional commands, e-mail: [email protected]
