I think 1.0 release in particular should be a relatively stable release, since we go from "beta"(?) stage of 0.x to 1.0. Otherwise, what prevents us from promoting 0.14 to 1.0? 0.14.1 is not done yet, so it would be great, we will have no 0.x.y releases, and 1.1 will become the first fix release, no confusion.
On Tue, Dec 2, 2014 at 8:05 PM, Xuefu Zhang <xzh...@cloudera.com> wrote: > Major release means more functionality, while minor releases provides > stability. Therefore, I'd think, 1.0, as a major release, should bring in > something new to the user. If it's desirable to provide more stable > release, then 0.14.1, 0.14.2, and so on are the right ones. In my opinion, > we should avoid doing anti-pattern by introducing major release like a > maintenance release and creating confusions among users. > > In one word, major release is NOT equal to major confusion. > > --Xuefu > > On Tue, Dec 2, 2014 at 7:29 PM, Sergey Shelukhin <ser...@hortonworks.com> > wrote: > > > I think it's better to do 1.0 release off a maintenance release, since > that > > is more stable. Trunk is moving fast. > > HBase uses odd release numbers for this purpose, where 0.95, 97, 99 etc. > > are dev releases and 0.96, 0.98, 1.0 etc. are public; that works well for > > baking, but since we don't have that seems like 14.0 would be a good > place > > to bake. 15.0 with bunch of new bugs that we are busy introducing may not > > be as good for 1.0 IMHO... > > > > On Tue, Dec 2, 2014 at 7:21 PM, Brock Noland <br...@cloudera.com> wrote: > > > > > Hi Thejas, > > > > > > Thank you very much for your proposal! > > > > > > Hadoop did something similar renaming branches to branch-1 and > > > branch-2. At the time, although I was very much in favor of the new > > > release numbers, I thought it could have been handled better. Renaming > > > release branches ended up being very confusing for users and I had a > > > ton of conversations with users about how releases were related. > > > > > > In this situation, I feel the situation is similar, we'll release 1.0 > > > which is really just the second maintainence release of the 0.14 > > > branch. Thus it's 1.0 but really it's just 0.14 + some fixes. I feel > > > this will again be confusing for users. For this important change, I > > > think we should use a new release vehicle. > > > > > > Thus, I'd suggest we do the rename in trunk, soon, and then the next > > > release of Hive will be 1.0. > > > > > > Cheers, > > > Brock > > > > > > On Tue, Dec 2, 2014 at 10:07 AM, Thejas Nair <the...@hortonworks.com> > > > wrote: > > > > Apache Hive is the de facto SQL query engine in the hadoop ecosystem. > > > > I believe it is also the most widely used one as well. Hive is used > in > > > > production in large number of enterprises. > > > > However, this 0.x.y versioning that we have been using for Hive > > > > obscures this status of Hive. > > > > > > > > I propose creating a 1.0 release out of the 0.14 branch of Hive. We > > > > already have some bug fixes for 0.14 release that have been added to > > > > the branch and a maintenance release is due. Having it out of this > > > > maintenance branch would create a better first 1.0 version, and we > > > > would be able to do it soon. What would have been 0.15 version would > > > > then become 1.1 version . > > > > > > > > Thoughts ? > > > > > > > > Thanks, > > > > Thejas > > > > > > > > -- > > > > CONFIDENTIALITY NOTICE > > > > NOTICE: This message is intended for the use of the individual or > > entity > > > to > > > > which it is addressed and may contain information that is > confidential, > > > > privileged and exempt from disclosure under applicable law. If the > > reader > > > > of this message is not the intended recipient, you are hereby > notified > > > that > > > > any printing, copying, dissemination, distribution, disclosure or > > > > forwarding of this communication is strictly prohibited. If you have > > > > received this communication in error, please contact the sender > > > immediately > > > > and delete it from your system. Thank You. > > > > > > > -- > > CONFIDENTIALITY NOTICE > > NOTICE: This message is intended for the use of the individual or entity > to > > which it is addressed and may contain information that is confidential, > > privileged and exempt from disclosure under applicable law. If the reader > > of this message is not the intended recipient, you are hereby notified > that > > any printing, copying, dissemination, distribution, disclosure or > > forwarding of this communication is strictly prohibited. If you have > > received this communication in error, please contact the sender > immediately > > and delete it from your system. Thank You. > > > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
