Re: Created branch 1.0

The build check in HIVE-8933 fixed in HIVE-8845. On Mon, Feb 9, 2015 at 11:32 AM, Vikram Dixit K wrote: > Hi Ed, > > This was the case with 0.14. It was fixed before 1.0 went out in HIVE-8933. > > Thanks > Vikram. > > On Mon, Feb 9, 2015 at 9:08 AM, Alan Gates wrote: > >> That's fixed, correct?

Re: Created branch 1.0

Hi Ed, This was the case with 0.14. It was fixed before 1.0 went out in HIVE-8933. Thanks Vikram. On Mon, Feb 9, 2015 at 9:08 AM, Alan Gates wrote: > That's fixed, correct? I do not believe there were any SNAPSHOT > dependencies in 1.0. > > Alan. > > Edward Capriolo > February 9, 2015 at

Re: Created branch 1.0

That's fixed, correct? I do not believe there were any SNAPSHOT dependencies in 1.0. Alan. Edward Capriolo February 9, 2015 at 8:40 Because we can not really have a stable api if by definition we build around snapshot dependencies. On Mon, Feb 9, 2015 at 11:38

Re: Created branch 1.0

rather than making it >> a >> >> feature release. >> >> >> >> @Lefty, >> >> >> >> You are right in that branch 0.14 has been made 1.0. You are also right >> >> that 0.15 would be 1.1.0 and we should capture that. >&

Re: Created branch 1.0

t fixed in 0.14 and is fixed in > >> 1.0 would have 1.0 as the fixed version. > >> Yes, 0.15.0 would then become 1.1.0 . > >> > >> Yes, it is a good idea to document this translation somewhere. > >> > >> > >> On Wed, Jan 21, 2015 at 3:

Re: Created branch 1.0

Hi, Yes as my main concern was that the 1.0 release would delay the subsequent release. If we are ready to do RC's now, I find this plan acceptable. Thank you for working hard to get this rc out. Brock On Tue, Jan 27, 2015 at 12:28 PM, Vikram Dixit K wrote: > Hi Folks, > > It has been a few d

Re: Created branch 1.0

Hi Folks, It has been a few days and I have done all the work needed to produce a 1.0 RC and think it is better to have a vote on it. I still hope that we can have this release as 1.0 and Brock's release as 1.1. By the end of the day I think having more releases is a good thing for the community a

Re: Created branch 1.0

I think the way it is done in Hadoop space is better for Hadoop space (and better wrt consistency, us being in the Hadoop space). Because no single company or QA process controls or covers all the changes to the product, and some changes go unseen by every actor, stabilization period is a must...

Re: Created branch 1.0

We really didn't define 1.0 very well. The way HBase did this (correct me if I'm wrong) is that 1.0 was the stable release (stable APIs and code). Then 1.1, 1.2 etc. become patch releases, and 2.0 becomes the release for all the new crazy stuff... On Fri, Jan 23, 2015 at 4:01 PM, Lefty Leverenz w

Re: Created branch 1.0

Setting aside branching specifics for a moment, what are the pros & cons of doing release 1.0 now or later? - From a documentation point of view, planning a later 1.0 release could give us time to catch up on the backlog of doc tasks, or at least prioritize the backlog and address the mos

Re: Created branch 1.0

Wherever I've seen in enterprise software, the trunk-based development model has been the standard where all release branches are cut from trunk and short-lived. I've never heard of a case where a branch originally designated for 0.14 (minor release) is cut again to become 1.0 (major release), and

Re: Created branch 1.0

On 1/23/15, 6:59 AM, Xuefu Zhang wrote: While it's true that a release isn't going to include everything from trunk, proposed 1.0 release is branched off 0.14, which was again branched from trunk long time ago. If you compare the code base, you will see the huge difference. From the stability a

Re: Created branch 1.0

anslation somewhere. > > > > > > On Wed, Jan 21, 2015 at 3:28 PM, Lefty Leverenz > > > > > wrote: > > > So my initial impression was correct -- instead of calling it release > > > 0.14.1, we're calling it 1.0.0. Or am I hopelessly conf

Re: Created branch 1.0

> Every release of hive has been a subset of tip of the trunk (we branch > for release while trunk moves ahead), and super set of changes of > every previous release. So every release so far has had a subset of > functionality of hive trunk branch (if that is what you are referring > to). While it

Re: Created branch 1.0

gt;> >> Yes, it is a good idea to document this translation somewhere. >> >> >> On Wed, Jan 21, 2015 at 3:28 PM, Lefty Leverenz >> >> wrote: >> > So my initial impression was correct -- instead of calling it release >> > 0.14.1, we're c

Re: Created branch 1.0

On Thu, Jan 22, 2015 at 2:49 PM, Edward Capriolo wrote: > If we do a 1.0.0 release there is no problem with us later releasing 14.1 > or a 14.2. I think everyone would understand that the 14.2 being released > after 1.0.0 would likely have back ported features. Releasing a 15.0 after > 1.0 would n

Re: Created branch 1.0

On Thu, Jan 22, 2015 at 12:31 PM, Xuefu Zhang wrote: > Hi Thejas/Alan, > > From all the argument, I think there was an assumption that the proposed > 1.0 release will be imminent and 0.15 will happen far after that. Based on > that assumption, 0.15 will become 1.1, which is greater in scope than 1

Re: Created branch 1.0

cument this translation somewhere. > > > > > > On Wed, Jan 21, 2015 at 3:28 PM, Lefty Leverenz > > > > > wrote: > > > So my initial impression was correct -- instead of calling it release > > > 0.14.1, we're calling it 1.0.0. Or am I hopelessly

Re: Created branch 1.0

dit a dozen wikidocs.) > > > > Will release numbers get changed in JIRA issues? Presumably that's not > > possible in old comments, so we should document the equivalences > > somewhere. A JIRA issue for that with a well-phrased summary could help > > future search

Re: Created branch 1.0

HIVE-9390 & HIVE-9404? This has been committed to trunk. >> They add useful retry logic to support insert/update/delete functionality. >> >> On Wed, Jan 21, 2015 at 1:06 PM, Vikram Dixit K < vikram.di...@gmail.com > >> wrote: >> >> > Hi Folks,

Re: Created branch 1.0

;>> >>>>>> >>>>>> On Wed, Jan 21, 2015 at 3:28 PM, Lefty Leverenz < >>>>>> leftylever...@gmail.com> >>>>>> wrote: >>>>>> > So my initial impression was correct -- instead of calling it release >>>>>

Re: Created branch 1.0

>> > Will 0.15.0 be 1.1.0? (If so, I'll need to edit a dozen wikidocs.) >>>>> > >>>>> > Will release numbers get changed in JIRA issues? Presumably that's not >>>>> > possible in old comments, so we should document the equivalences >&

Re: Created branch 1.0

On Wed, Jan 21, 2015 at 7:09 PM, Brock Noland wrote: > Sorry about the confusion. That link misses the content to which I was > replying. I agree that 1.0 should be stable, but that does not mean that I > agree that 1.0 should come from 0.14. For a stable release, we would need to go through an

Re: Created branch 1.0

be 1.1.0? (If so, I'll need to edit a dozen wikidocs.) >>>> > >>>> > Will release numbers get changed in JIRA issues? Presumably that's not >>>> > possible in old comments, so we should document the equivalences >>>> > somewhere. A

Re: Created branch 1.0

t; They add useful retry logic to support insert/update/delete functionality. >> >> On Wed, Jan 21, 2015 at 1:06 PM, Vikram Dixit K < vikram.di...@gmail.com > >> wrote: >> >> > Hi Folks, >> > >> > I have created branch 1.0 as discusse

Re: Created branch 1.0

orks.com> >> > wrote: >> > >> >> could we include HIVE-9390 & HIVE-9404? This has been committed to >> trunk. >> >> They add useful retry logic to support insert/update/delete >> functionality. >> >> >> >> On Wed, Jan 21, 2015 a

Re: Created branch 1.0

koif...@hortonworks.com> > > wrote: > > > >> could we include HIVE-9390 & HIVE-9404? This has been committed to > trunk. > >> They add useful retry logic to support insert/update/delete > functionality. > >> > >> On Wed, Jan 21, 2

Re: Created branch 1.0

HIVE-9390 & HIVE-9404? This has been committed to trunk. >> They add useful retry logic to support insert/update/delete functionality. >> >> On Wed, Jan 21, 2015 at 1:06 PM, Vikram Dixit K >> wrote: >> >> > Hi Folks, >> > >> > I have creat

Re: Created branch 1.0

could help >> future searchers. >> >> >> -- Lefty >> >> On Wed, Jan 21, 2015 at 2:47 PM, Eugene Koifman >> wrote: >> >>> could we include HIVE-9390 & HIVE-9404? This has been committed to trunk. >>> They add useful retry logic

Re: Created branch 1.0

itted to trunk. >> They add useful retry logic to support insert/update/delete functionality. >> >> On Wed, Jan 21, 2015 at 1:06 PM, Vikram Dixit K >> wrote: >> >> > Hi Folks, >> > >> > I have created branch 1.0 as discussed earlier. All the jiras

Re: Created branch 1.0

unk. > They add useful retry logic to support insert/update/delete functionality. > > On Wed, Jan 21, 2015 at 1:06 PM, Vikram Dixit K > wrote: > > > Hi Folks, > > > > I have created branch 1.0 as discussed earlier. All the jiras that have > > 0.14 as the fix

Re: Created branch 1.0

could we include HIVE-9390 & HIVE-9404? This has been committed to trunk. They add useful retry logic to support insert/update/delete functionality. On Wed, Jan 21, 2015 at 1:06 PM, Vikram Dixit K wrote: > Hi Folks, > > I have created branch 1.0 as discussed earlier. All the ji

Re: Created branch 1.0

Vikram, Which branch was the 1.0 branch created from? Brock On Jan 21, 2015 1:07 PM, "Vikram Dixit K" wrote: > Hi Folks, > > I have created branch 1.0 as discussed earlier. All the jiras that have > 0.14 as the fix version should be committed to 1.0 branch instead. The li

Created branch 1.0

Hi Folks, I have created branch 1.0 as discussed earlier. All the jiras that have 0.14 as the fix version should be committed to 1.0 branch instead. The list of jiras that are being tracked for 1.0 are as follows: HIVE-8485 HIVE-9053 HIVE-8996. Please let me know if you want to include more