Okay. Makes sense. Thanks, Xuefu
On Tue, Mar 31, 2015 at 11:38 AM, Thejas Nair <thejas.n...@gmail.com> wrote: > Xuefu, > Releases such as 1.1.1 are by convention bug fix releases, and only > include a selected set of important bug fixes that have been applied > to the release branch (branch-1.1 in this case). > > In the 2 months since the creation of branch-1.0, we have around 211 > jiras that have been committed in trunk (fix version 1.2.0). I would > expect around another 100 to go in, with the timeline proposed above. > > > https://issues.apache.org/jira/browse/HIVE-9727?jql=project%20%3D%20HIVE%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%201.2.0%20ORDER%20BY%20updatedDate%20DESC > > Maintenance releases of branch-1.1 and earlier branches can continue > irrespective of a new release from trunk. > > > > On Tue, Mar 31, 2015 at 7:05 AM, Xuefu Zhang <xzh...@cloudera.com> wrote: > > Hi Sushanth, > > > > Thanks for starting this. Rapid releasing is good. However, could you > > please provide a list of major changes or enhancement? I'd like to see > > whether we are in position to release it as 1.1.1 or 1.2.0. > > > > Thanks, > > Xuefu > > > > On Mon, Mar 30, 2015 at 10:02 AM, Sushanth Sowmyan <khorg...@gmail.com> > > wrote: > > > >> Hi Folks, > >> > >> Given that we landed a bunch of changes in trunk shooting for 1.2 > >> after 1.1 was forked off, including some metastore changes, I propose > >> that we have a feature rollup release of hive that matches the state > >> of trunk sooner rather than later. For the timeline, I was thinking > >> that it'd be ideal to fork around Apr 18th(Friday), and try to get RCs > >> going within a couple of days, and a release by the end of > >> April/beginning of May. > >> > >> I would like to volunteer to perform the duties of a release manager > >> for this if there is enough appeal for this. > >> > >> Thanks > >> >
