To be clear, I think we all seem to agree that we continue to make
hadoop-2.0.3, hadoop-2.0.3 etc. with alpha/beta tags as appropriate until we
git 'GA' at which point we release hadoop-2.1.0. Makes sense?
thanks,
Arun
On Sep 6, 2012, at 11:38 AM, Arun C Murthy wrote:
> Uh, I meant 'create had
Uh, I meant 'create hadoop-2.0.2-alpha' release off branch-2.
On Sep 6, 2012, at 11:18 AM, Arun C Murthy wrote:
> Sounds fine.
>
> For now, I think we can delete branch-2.1.0-alpha, create branch-2.0.2-alpha
> release off branch-2 and eventually make branch-2.1.0 as the stable release
> in the
Sounds fine.
For now, I think we can delete branch-2.1.0-alpha, create branch-2.0.2-alpha
release off branch-2 and eventually make branch-2.1.0 as the stable release in
the future.
Arun
On Sep 4, 2012, at 11:55 AM, Owen O'Malley wrote:
> While cleaning up the subversion branches, I thought mo
No, thanks Owen.
On Thu, Sep 6, 2012 at 9:27 AM, Owen O'Malley wrote:
> On Wed, Sep 5, 2012 at 11:04 AM, Andrew Purtell
> wrote:
> > If it's all the same to you, I'd prefer you leave the branch, or at
> least a
> > tag, and just ignore it. We're pretty far away from branch-2.1.0
> following
> >
On Wed, Sep 5, 2012 at 11:04 AM, Andrew Purtell wrote:
> If it's all the same to you, I'd prefer you leave the branch, or at least a
> tag, and just ignore it. We're pretty far away from branch-2.1.0 following
> branch-2 but started from that point.
Subversion you don't actually ever delete anyth
If it's all the same to you, I'd prefer you leave the branch, or at least a
tag, and just ignore it. We're pretty far away from branch-2.1.0 following
branch-2 but started from that point.
On Wed, Sep 5, 2012 at 8:52 AM, Eli Collins wrote:
> On Tue, Sep 4, 2012 at 11:55 AM, Owen O'Malley wrote:
On Tue, Sep 4, 2012 at 11:55 AM, Owen O'Malley wrote:
> While cleaning up the subversion branches, I thought more about the
> branch 2 release names. I'm concerned if we backtrack and reuse
> release numbers it will be extremely confusing to users. It also
> creates problems for tools like Maven t
2012 7:29 PM
To: "common-dev@hadoop.apache.org<mailto:common-dev@hadoop.apache.org>"
mailto:common-dev@hadoop.apache.org>>
Subject: Re: Branch 2 release names
May be you misread the proposal. This is only about nuking 2.1.0-alpha and wait
for 0.23.3 to be stabilized and releas
May be you misread the proposal. This is only about nuking 2.1.0-alpha and wait
for 0.23.3 to be stabilized and released. Once that happens, we can create a
branch-2.1 off branch-2.
Does that sound okay?
Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/
On Sep 4, 2012,
I am fine with that too, but it is going to be a fairly large amount of
work to pull in all of the bug fixes into 2.0 that have gone into 0.23.
There was already a lot of discussion about just rebasing 2.1 instead of
trying to merge everything back into it and 2.1 is a lot further along
then 2.0 is
+1 for moving on with 2.0 till it gets GA'ed, given we haven't made much
progress on 2.0.1-alpha.
+1 for putting the alpha/beta tags only on releases, and not on branches.
This also reduces some branch-clutter like I mentioned on the other thread on
general@h.a.o.
Thanks,
+Vinod
On Sep 4, 20
11 matches
Mail list logo
