[
https://issues.apache.org/jira/browse/OOZIE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178927#comment-13178927
]
Harsh J commented on OOZIE-433:
-------------------------------
This may still be relevant for now we're at Apache and these processes need to
be documented for committers? :)
> OOZIE-16: Defining the release closing process
> ----------------------------------------------
>
> Key: OOZIE-433
> URL: https://issues.apache.org/jira/browse/OOZIE-433
> Project: Oozie
> Issue Type: Task
> Reporter: Hadoop QA
> Assignee: Roman Shaposhnik
>
> At the end of any release, there are some steps that needs to be followed.
> This issue is to discuss and finalize those steps and then document it.
> I want to start with some, please add more if needed. Later, I will add a
> wiki on this.
> * Review all open Pull Requests (PR).
> * Push all PRs that are needed/relevant for that release.
> * Rest of PRs needs to be withdrawn or closed. <Please verify this!!>
> * Review the bugs in ISSUE/JIRA that are tagged for the specific release.
> * Move the issue or jira that are originally tagged for the targeted release
> but not implemented. (Question: how to *modify* label in issue?).
> * Add the specific release document link in the main page (i.e.
> http://yahoo.github.com/oozie/).
> * Send email communication to user-group for the upcoming release.
> * PLEASE ADD/UPDATE.......
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
