hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter S <htims.r...@gmail.com>
Subject Re: a newbie question
Date Thu, 02 Feb 2012 04:45:00 GMT
Hi Harsh,

Thanks a lot for the reply.  Some questions are inline.

On Wed, Feb 1, 2012 at 8:31 PM, Harsh J <harsh@cloudera.com> wrote:

> Peter,
> (Inline)
> On Thu, Feb 2, 2012 at 3:06 AM, Peter S <htims.rm.p@gmail.com> wrote:
> > I realize the version numbers are actually different branches, e.g.
> > branch-0.21, branch-0.22, branch-0.23, and trunk. I am wondering which
> > branch should I use and develop on? Which one is most stable?
> All new work is to go to trunk (presently numbered as 0.24).

Then how about 1.0.*?  It seems in the beta version. But why trunk number
is still 0.24?


> The page at http://wiki.apache.org/hadoop/HowToContribute goes over
> setting up the trunk development workspace and should help you get
> started.
> What do you mean by "most stable"? Do you ask in terms of build stability?
I mean in production.  From the release page:
0.20.X - legacy stable version
0.20.203.X - current stable version
1.0.X - current beta version, 1.0 release
0.22.X - does not include security
0.23.X - current alpha version
I don't quite get this. Why 0.23.X is in alpha version, but 1.0.X is in
beta version? And the 0.22.X doesn't include security. How does this
release number work?

For Cloudera version, will all the patches in CDH also in 1.0.X?

> > Does trunk include all patches in other branches such as branch-0.21?
> Yes, the branches are progressive.
> >
> > For hadoop common repo, which version should I use for a particular hdfs
> > version?
> Don't quite get this question.
Because common repo and hdfs repo is separate, is it possible to have some
incompatibility between the two.

> > Also, I realize the git repo is not updated on time when code is
> committed
> > to the svn repo. Should I use the git repo for dev or build a local git
> > repo on top of svn repo instead?
> Using a slightly-lagged git mirror or the subversion repository is
> your choice -- I prefer to use the former while working. The only part
> to remember about using git is to use the --no-prefix operator in
> git-diff command while generating patches for contribution via the
Got it. Thanks a  lot.

> --
> Harsh J
> Customer Ops. Engineer
> Cloudera | http://tiny.cloudera.com/about

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