Karthik Kambatla created MAPREDUCE-4973:
---
Summary: Backport history clean up configurations to branch-1
Key: MAPREDUCE-4973
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4973
Project: Hado
On Thu, Jan 31, 2013 at 12:12 PM, Arun C Murthy wrote:
> I apologize if there was too much technical details.
>
> The simplified version is that hadoop-2 isn't baked as it stands today,
> and is not viable to be supported by this community in a stable manner. In
> particular, it is due to the mov
On Fri, Feb 1, 2013 at 2:34 AM, Tom White wrote:
> Possibly the reason for Stack's consternation is that this is a
> Hadoop-specific versioning scheme, rather than a standard one like
> Semantic Versioning (http://semver.org/) which is more widely
> understood.
If I can offer an alternate and l
Arun C Murthy created MAPREDUCE-4971:
Summary: Minor extensibility enhancements
Key: MAPREDUCE-4971
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4971
Project: Hadoop Map/Reduce
I
On Wed, Jan 30, 2013 at 11:32 PM, Vinod Kumar Vavilapalli
wrote:
> I still have a list of pending API/protocol cleanup in YARN that need to be
> in before we even attempt supporting compatibility further down the road.
To let others track these it would be useful if they were tagged in
JIRA with
Possibly the reason for Stack's consternation is that this is a
Hadoop-specific versioning scheme, rather than a standard one like
Semantic Versioning (http://semver.org/) which is more widely
understood.
With that scheme we would have something like
2.0.0-alpha, 2.0.0-alpha.1, 2.0.0-alpha.2, 2