[
https://issues.apache.org/jira/browse/HADOOP-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628607#action_12628607
]
Steve Loughran commented on HADOOP-3979:
----------------------------------------
we have specific release and (test release) VMware images @work for cutting
releases
http://smartfrog.svn.sourceforge.net/viewvc/smartfrog/trunk/core/release/doc/creating_release_artifacts.sxw
This works well as you can do a release test in the background while editing
your local copy, and the release machine account lacks the ability to commit
changes; nobody ever edits stuff there or fiddles with the settings to meet
local developer needs.
The biggest problem is that 24h before the release you need to bring the images
up to date, and that can break the build; one update of RHEL5 switched java
back to gcj, for example.
It should be possible to create a 64-bit CentOS or ubuntu vmware image to share
around for people cutting releases, just rather large.
> linux 64-bit native libraries should always be built and included in release
> ----------------------------------------------------------------------------
>
> Key: HADOOP-3979
> URL: https://issues.apache.org/jira/browse/HADOOP-3979
> Project: Hadoop Core
> Issue Type: Wish
> Components: build, native
> Reporter: Rong-En Fan
> Priority: Minor
>
> The current HowToRelease wiki document says that 64-bit linux native libs are
> optional for a release. However, we had them in all 0.16.x, 0.17.[0-1], and
> 0.18.0 releases. Provided the fact that 64-bit computers become more common
> nowadays. We should make this binary built and included in release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
