I will look into making an overview. Yes, DOC JIRAs would need to be addressed too. Are these all external docs I.e. wiki?
On 15/11/10, 18:49, "Lefty Leverenz" <leftylever...@gmail.com> wrote: >The overview could go into the wiki when the time comes, along with 38 or >more doc fixes (which I'm sure people will rush to finish before the >release): TODOC2.0 ><https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20l >abels%20%3D%20TODOC2.0%20ORDER%20BY%20assignee%20ASC> >. > >-- Lefty > > >On Tue, Nov 10, 2015 at 5:04 PM, Xuefu Zhang <xzh...@cloudera.com> wrote: > >> I understand that there have been a lot of things that have been added >>or >> merged to master. However, I think many of us has no clear picture where >> things are, especially about new features and their stability/usability. >> Thus, I think it would be great if someone can give an high-level >>overview >> on what we are releasing and the watermark on the quality ladder. This >> should help us decide if it's time... >> >> Thanks, >> Xuefu >> >> >> On Tue, Nov 10, 2015 at 1:46 PM, Thejas Nair <thejas.n...@gmail.com> >> wrote: >> >> > +1 >> > It would be good to let users play with some of the new features and >> > give feedback. >> > >> > Regarding the vote, we don't have a precedent for conducting that for >> > a release proposal. So this discussion thread should be sufficient, >> > unless someone feels otherwise. >> > There will certainly be a vote on the RC. >> > >> > >> > On Tue, Nov 10, 2015 at 11:58 AM, Sergey Shelukhin >> > <ser...@hortonworks.com> wrote: >> > > Hi. >> > > I would like to start the discussion about the first Hive 2 release >>and >> > > volunteer to be a release manager. >> > > The branch has existed for a while and has a lot of new exciting >> > features. >> > > >> > > If there are no objections, I’ll start a VOTE thread soon. Please >>mark >> > the >> > > unfinished features that you’d like to go in, and must-fix bugs via >> > Target >> > > Version field in the JIRAs; we can cut the branch late next weeks >> > assuming >> > > the vote passes (by which time the features that are ready to go >>should >> > > mostly be in), and work on fixing bugs and making an RC. >> > > >> > > >> > > >> > >>
