Hey,

Just a few questions I had. I was trying to figure out what the bigger
roadmap is for hadoop. I've read the roadmap on the wiki and jira and
it's not super clear for me, what the plan is for 21.

- Was curious if and when 21.1 was going to be branched/Are there a
set of features pending until this is started?
- Would it make sense to change 21.1 and 22.0 on the roadmap in jira
and svn to actually be 21.201/22.200, for consistency?
- Will there be a minor release on 20-appends to fix security issues
https://issues.apache.org/jira/browse/HADOOP/fixforversion/12315102?
This would however mess up the current versioning system, but I think
would be good to support a stable version that doesn't require
patching on the end user/consumer side, especially when the patches
seem readily available, but not officially taged as a release.

Thanks,
Luke

On Wed, Aug 24, 2011 at 5:23 AM, Luke Weber <[EMAIL PROTECTED]> wrote:

> Hey,
>
> Just a few questions I had. I was trying to figure out what the bigger
> roadmap is for hadoop. I've read the roadmap on the wiki and jira and
> it's not super clear for me, what the plan is for 21.
>

0.21 is not considered stable and has never been tested at scale. At the
current time, no committers have volunteered to drive the next release off
of that branch. Arun is close to branching 0.23 from trunk, but it will take
some time to stabilize.

For stable releases, I'd suggest 0.20.203.0 or the upcoming 0.20.204.0. Over
on general@hadoop, there is a discussion of getting content into 0.20.205 or
later stable releases.
> - Would it make sense to change 21.1 and 22.0 on the roadmap in jira
> and svn to actually be 21.201/22.200, for consistency?
>

The problem is that the 0.20.2xx releases are neither a superset or subset
of the 0.21 release. In many ways, the 0.20.2xx.y releases would be better
named as 1.x.y.

-- Owen

>
>
>
>The problem is that the 0.20.2xx releases are neither a superset or subset
>of the 0.21 release. In many ways, the 0.20.2xx.y releases would be better
>named as 1.x.y.

This confused me totally. Is the thinking to make 0.20.2xx.y as 1.x.y or
is it 0.23.x which will become 1.x.y ?

- milind

On Aug 25, 2011, at 1:07 PM, <[EMAIL PROTECTED]>
 <[EMAIL PROTECTED]> wrote:

>>
>>
>>
>> The problem is that the 0.20.2xx releases are neither a superset or subset
>> of the 0.21 release. In many ways, the 0.20.2xx.y releases would be better
>> named as 1.x.y.
>
> This confused me totally. Is the thinking to make 0.20.2xx.y as 1.x.y or
> is it 0.23.x which will become 1.x.y ?

1.x.y will be 1.x.y.