hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Lipcon <t...@cloudera.com>
Subject Re: Contributing a New FileSystem Implementation - Questions About Process
Date Mon, 10 Aug 2009 20:35:38 GMT
Hi Jonathan,

Responses inline below:

On Mon, Aug 10, 2009 at 1:28 PM, Jonathan Seidman <
jonathan.seidman@opendatagroup.com> wrote:

> We're getting ready to contribute our FileSystem implementation for the
> Sector DFS (sector.sf.net). Up to now our development and testing has been
> against 0.18.3, so our intention was to first integrate with that release
> and then work on integrating with the trunk for the next release. A couple
> of questions:

> * Should we integrate with the 0.18 branch, or just put our changes into
> the
> 0.18.3 release? We're not sure if there are plans for further releases on
> the 0.18  branch.

I believe there are plans for an 0.18.4 release eventually, though a new
feature like a new DFS is unlikely to be included. I would concentrate on
integrating against trunk rather than a past release. If trunk is
inconvenient since it's a moving target, you could integrate against
branch-20. While a lot of people are currently using 0.18, I anticipate that
most users will be switching over to 0.20 in the next couple of months.

> * Should we create separate Jira's for the two releases, or can we create a
> single Jira to cover the 0.18 and trunk releases?

Single JIRA should be fine - just post multiple patches.

> Thanks for your help. We'd like to make sure we're facilitating the
> process,
> so any suggestions are appreciated.

In general you should be aware that you should integrate as a new project in
the contrib/ dir. If all goes well you shouldn't need to make any patches
that touch Hadoop itself.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message