Hi Folks, As per the timeline set on https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status , the time for requests for inclusion of any new features to branch-1.2 is now closed. Any JIRAS already marked in the lists previously will be honoured and considered release blockers, but no new feature JIRAs will be included.
The list is still open for any new bugfix jira to be added to the list. I will start getting RC0 ready now. The purpose of RC0 is not for it to be a true release-candidate, but simply to go through the process of creating a release, verifying instructions set to create a release, so that we can discover any hiccups along the way. Once that is done, the next deadline of note for the community is 15:01, Thursday, 30th Apr 2015 PDT, which is the deadline for requesting any bugfix jiras for inclusion. After this deadline, the list will go into further lockdown, and allow inclusion of only jiras already in the currently accepted lists, and either critical bugfixes which are product breakages without workarounds, or bugs discovered during testing of the RCs. Thanks, -Sushanth On Mon, Apr 27, 2015 at 4:51 PM, Sushanth Sowmyan <khorg...@gmail.com> wrote: > HIVE-10509 and HIVE-10510 have been created with the individual > patches that upgraded master and branch-1.2 respectively, and marked > as resolved. > > I'll also add it in to the HowToRelease doc to ensure that from the > next release onward, we create a jira for this. > > Also, friendly reminder for folks : If you have any other jira you > want included for 1.2, please go and add it to > https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status > > Tonight midnight will be the deadline for feature include requests, > and this list will go on lockdown for any further requests for feature > inclusions. Bugfixes will still be okay to request for inclusion. > > > > On Mon, Apr 27, 2015 at 4:41 PM, Sushanth Sowmyan <khorg...@gmail.com> wrote: >> Also, Agreed with Sergio/Szehon, we should have a jira that's marked >> as committed with a patch attached for the version bump patch. >> Creating one. >> >> On Mon, Apr 27, 2015 at 4:39 PM, Sushanth Sowmyan <khorg...@gmail.com> wrote: >>> Vinod, >>> >>> If 2.7.0 is "not-yet-ready", then we should not be bumping 1.2 to >>> 2.7.0. But, we should be okay to bump master(1.3) up to 2.7.0 so that >>> we start general-purpose testing against that. >>> >>> Please go ahead and create a jira for that, and we should be able to >>> bump up trunk to go against that. >>> >>> Thanks, >>> -Sushanth
