On Sun, Jun 02, 2013 at 09:17PM, Arun C Murthy wrote:
> I do it in the release branch, so the release source tarball has the date.
I guess 2.0.4-alpha was cut differently for whatever reason, 'cause i see the
UNRELEASED date in the source tarball.
As I said - if anyone feels strongly about it I w
I do it in the release branch, so the release source tarball has the date.
Arun
On Jun 2, 2013, at 6:41 PM, Konstantin Boudnik wrote:
> On Sun, Jun 02, 2013 at 03:04PM, Arun C Murthy wrote:
>> I record the 'release date' as the one on which the build is created. Not
>> sure what Matt actually do
[
https://issues.apache.org/jira/browse/MAPREDUCE-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth resolved MAPREDUCE-5291.
---
Resolution: Fixed
Fix Version/s: 2.1.0-beta
Hadoop Flags: Reviewed
Co
Siddharth Seth created MAPREDUCE-5291:
-
Summary: Change MR App to use update property names in
container-log4j.properties
Key: MAPREDUCE-5291
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5291
On Sun, Jun 02, 2013 at 03:04PM, Arun C Murthy wrote:
> I record the 'release date' as the one on which the build is created. Not
> sure what Matt actually does on branch-1. Matt?
Arun, but you do this not in the release source tarball, right? Just in the
rest of integration branches, ie branch-2
[
https://issues.apache.org/jira/browse/MAPREDUCE-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved MAPREDUCE-3859.
--
Resolution: Fixed
Fix Version/s: (was: 2.1.0-beta)
I'm resolving this fo
Arun C Murthy created MAPREDUCE-5290:
Summary: CLONE - CapacityScheduler incorrectly utilizes
extra-resources of queue for high-memory jobs
Key: MAPREDUCE-5290
URL: https://issues.apache.org/jira/browse/MAPRED
I record the 'release date' as the one on which the build is created. Not sure
what Matt actually does on branch-1. Matt?
hth,
Arun
On Jun 2, 2013, at 12:33 PM, Konstantin Boudnik wrote:
> This is my first Hadoop release, so I am all ears ;) I looked at how Arun was
> cutting the previous 2.0.x
+1
Did basic verification and testing.
Thanks,
--Konst
On Fri, May 31, 2013 at 9:27 PM, Konstantin Boudnik wrote:
> All,
>
> I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I
> would
> like to release.
>
> This is a stabilization release that includes fixed for a couple a
This is my first Hadoop release, so I am all ears ;) I looked at how Arun was
cutting the previous 2.0.x and followed the example.
Thanks for your input and help Alejandro!
Regards,
Cos
On Sun, Jun 02, 2013 at 09:01AM, Alejandro Abdelnur wrote:
> I know we had this issue before. But and easy
I know we had this issue before. But and easy way to solve it it would be using
as release date the date the vote ends. Anyway, not a big deal if we are not
cutting a new rc for other reason
+1 on rc1
Thx
On Jun 2, 2013, at 12:04 AM, Konstantin Boudnik wrote:
> Alejandro,
>
> I believe this
Alejandro,
I believe this is chicken and egg problem: I can't put release date into
unreleased tarball. Looking into 2.0.4-alpha source tarball I see the same
situation:
Release 2.0.4-alpha - UNRELEASED
But in the trunk and branch-2 the release data is in place. I don't think this
is an issue. B
12 matches
Mail list logo
