From: Steve L. (JIRA) <ji...@sm...> - 2009-08-14 16:01:10
|
[ http://jira.smartfrog.org/jira/browse/SFOS-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11797#action_11797 ] Steve Loughran commented on SFOS-1269: -------------------------------------- Common patch is https://issues.apache.org/jira/browse/HDFS-326 HDFS patch is HDFS-545 https://issues.apache.org/jira/browse/HDFS-545 Branches root https://issues.apache.org/jira/browse/HDFS-326 common https://issues.apache.org/jira/browse/HADOOP-6194 mapred https://issues.apache.org/jira/browse/MAPREDUCE-233 SVN repositories original: svn co https://svn.apache.org/repos/asf/hadoop/common/branches/HADOOP-3628-2/ hadoop-3628-2 Merge this in with the pre-split branch https://svn.apache.org/repos/asf/hadoop/common/branches/pre-HADOOP-4687/ > Catch up my patches with Hadoop core > ------------------------------------ > > Key: SFOS-1269 > URL: http://jira.smartfrog.org/jira/browse/SFOS-1269 > Project: SmartFrog > Issue Type: Task > Components: _service_hadoop > Affects Versions: 3.17.x > Reporter: Steve Loughran > Assignee: Steve Loughran > Fix For: 3.17.x > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Bring my patches up to SVN head. Here is the action list > 1. check out the new repositories, make sure the tests work (common test is fast, hdfs slow, mapred slower) > 2. create Apache jira issues for > Add Service Lifecycle to common > Add Service Lifecycle to HDFS > Add Service Lifecycle to mapred > 3. Create a branch for each of the new forks and check out > 4. Apply the original patch to each one, so creating 3 new (patched) branches > 5. create the diffs (build file is set up to do this) > 6. Attach the diffs to the patches > 7. update the documents -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |