Message-
From: Joydeep Sen Sarma [mailto:jssa...@facebook.com]
Sent: Tuesday, March 10, 2009 11:37 AM
To: hive-dev@hadoop.apache.org
Subject: RE: branching Hive and getting to first release
I am in general agreement - but the problems is the mail below doesn't
explain why trunk
as hadoop
does...
Ashish
-Original Message-
From: Jeff Hammerbacher [mailto:ham...@cloudera.com]
Sent: Thursday, March 26, 2009 11:19 AM
To: hive-dev@hadoop.apache.org
Subject: Re: branching Hive and getting to first release
Hey,
What's the state of the release process? We'd really
a stable version out...
Thoughts?
Ashish
-Original Message-
From: Johan Oskarsson [mailto:jo...@oskarsson.nu]
Sent: Tuesday, March 03, 2009 2:54 AM
To: hive-dev@hadoop.apache.org
Subject: Re: branching Hive and getting to first release
To be honest I must've missed
directly man .. :-)
-Original Message-
From: Johan Oskarsson [mailto:jo...@oskarsson.nu]
Sent: Tuesday, March 10, 2009 3:43 AM
To: hive-dev@hadoop.apache.org
Subject: Re: branching Hive and getting to first release
I'm worried that trying to create a new release every other week will be
too
this seems dubious to me.
Can't put a newborn into kindergarten directly man .. :-)
-Original Message-
From: Johan Oskarsson [mailto:jo...@oskarsson.nu]
Sent: Tuesday, March 10, 2009 3:43 AM
To: hive-dev@hadoop.apache.org
Subject: Re: branching Hive and getting to first release
@hadoop.apache.org
Subject: Re: branching Hive and getting to first release
I'm worried that trying to create a new release every other week will be
too often. Isn't there a risk that we're still fixing bugs in 0.3 when
the 0.5 branch is cut if we run into something unexpected?
It seems Hadoop
-Original Message-
From: Johan Oskarsson [mailto:jo...@oskarsson.nu]
Sent: Tuesday, March 10, 2009 9:52 AM
To: hive-dev@hadoop.apache.org
Subject: Re: branching Hive and getting to first release
+1, sounds like a solid plan.
Joydeep Sen Sarma wrote:
I am also a little worried about
@hadoop.apache.org
Subject: RE: branching Hive and getting to first release
I think a big reason for what killed 0.2 was the fact that we decided to deploy
trunk into production because of some features that the internal users were
asking for, instead of just continuing with the 0.2 branch. What I want
-
From: Joydeep Sen Sarma [mailto:jssa...@facebook.com]
Sent: Tuesday, March 10, 2009 11:37 AM
To: hive-dev@hadoop.apache.org
Subject: RE: branching Hive and getting to first release
I am in general agreement - but the problems is the mail below doesn't
explain why trunk was deployed
...
Thoughts?
Ashish
-Original Message-
From: Johan Oskarsson [mailto:jo...@oskarsson.nu]
Sent: Tuesday, March 03, 2009 2:54 AM
To: hive-dev@hadoop.apache.org
Subject: Re: branching Hive and getting to first release
To be honest I must've missed that 0.2 was branched (I found the email
To be honest I must've missed that 0.2 was branched (I found the email
now though), was there a feature freeze date set?
After branching shouldn't we have moved the non critical issues to 0.3
and pushed for fixing the remaining bugs in order to release?
That aside, I don't have a strong opinion
Hey folks,
A few of us were chatting earlier today (some Facebook and Cloudera folks) on
best approach to get to a first Hive release.
While 0.2 has been branched - it seems awkward to base the first release on it.
The reason is twofold:
- new changes to trunk since 0.2 have been
12 matches
Mail list logo
