[
https://issues.apache.org/jira/browse/BIGTOP-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shaposhnik updated BIGTOP-822:
------------------------------------
Attachment: 0001-BIGTOP-822.-Bump-version-of-Hadoop-to-2.0.4.patch
So here's what I propose (although I know it may sound a bit controversial) --
given the unique situation with Hadoop 2.0.4-alpha branch I propose we pull it
into our trunk now.
We *have* to wait for Hadoop 2.0.4-alpha to stabilize and we might as well give
everybody a benefit of pulling from the trunk.
New patch is attached. I'll keep the JIRA open to cut over to the tarball when
it gets released.
P.S. I have also split out the other bits into separate patches for now.
> Bump version of Hadoop to 2.0.4
> -------------------------------
>
> Key: BIGTOP-822
> URL: https://issues.apache.org/jira/browse/BIGTOP-822
> Project: Bigtop
> Issue Type: Sub-task
> Components: General
> Affects Versions: 0.5.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.6.0
>
> Attachments: 0001-BIGTOP-822.-Bump-version-of-Hadoop-to-2.0.4.patch,
> 0001-bump-version.patch, BIGTOP-822.patch.txt
>
>
> We need to take care of QJM as part of doing this BIGTOP-763. Perhaps it
> would be ok to be aggressive and start building based on branch-2 now, but we
> need to figure out what is the likelihood of 2.0.3 actually making it within
> the next couple of month
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
