+1 on dedicated release manager (thanks for volunteering, Mina!) On Thu, Jun 9, 2016 at 7:41 AM Felix Cheung <felixcheun...@hotmail.com> wrote:
> +1 on release branch+1 on dedicated release manager (thanks for > volunteering, Mina!) > > > > _____________________________ > From: mina lee <mina...@apache.org> > Sent: Wednesday, June 8, 2016 9:50 AM > Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release > To: <dev@zeppelin.apache.org> > > > Moon, I think it's good idea to cut the branch on 15 June. > As we discussed in previous release discussion thread [1], shall we take a > rotation for this release? > If so, I would like to volunteer this time. > > But in the end, I think it would be better to have one dedicated release > manager like other apache projects do. It takes time for every new release > manager to get familiar with apache release process, set the environment, > etc. And I expect for community to be more structured at release by having > release manager who can takes more about release time, release scope. > > regards, > mina > > [1] > > http://apache-zeppelin-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Release-0-5-6-incubating-td4728i20.html > > On Wed, Jun 8, 2016 at 8:34 AM, Guillaume Alleon < > guillaume.all...@gmail.com > > wrote: > > > Ho mon > > > > Do we have a branch using the preview release of spark 2.0? > > > > Cheers > > Guillaume > > > > Sent from a small device > > > > > On 08 Jun 2016, at 17:10, moon soo Lee <m...@apache.org> wrote: > > > > > > How about we create release branch 'branch-0.6' from master on 15 June, > > > 00:00 PDT, and start release process from that point? > > > > > > Most of TLP migration has been done (except for git source repo / > mirror > > > migration) and we can always create minor release with spark 2.0 > support > > if > > > spark 2.0 support is not ready when we cut the release branch. > > > > > > Thanks, > > > moon > > > > > >> On Wed, May 25, 2016 at 1:09 PM Vinay Shukla <vinayshu...@gmail.com> > > wrote: > > >> > > >> Agree, let's make our first release as a TLP. > > >> > > >> On Wednesday, May 25, 2016, Felix Cheung <felixcheun...@hotmail.com> > > >> wrote: > > >> > > >>> +1 on release.If we could sort out Spark 2.0 great, if not we should > > have > > >>> a release anyway. > > >>> > > >>> > > >>> > > >>> _____________________________ > > >>> From: Alexander Bezzubov <b...@apache.org <javascript:;>> > > >>> Sent: Tuesday, May 24, 2016 4:44 PM > > >>> Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release > > >>> To: <dev@zeppelin.apache.org <javascript:;>> > > >>> > > >>> > > >>> Thank you Moon for starting discussion, > > >>> I can not agree more - it's time for another release, our first one > as > > >> TLP! > > >>> > > >>> As you said - there are many improvements, more then enough for a new > > >>> release, but having Spark 2.0 profile there would be awesome. > > >>> > > >>> -- > > >>> Alex > > >>> > > >>> On Wed, May 25, 2016, 03:34 Luciano Resende <luckbr1...@gmail.com > > >>> <javascript:;>> wrote: > > >>> > > >>>> On Tue, May 24, 2016 at 11:30 AM, Jonathan Kelly < > > >> jonathaka...@gmail.com > > >>> <javascript:;>> > > >>>> wrote: > > >>>> > > >>>>> Of course, but it would still be possible for Zeppelin to support > > >> Spark > > >>>> 2.0 > > >>>>> using a Maven profile, right? (Handwaving the difficulty of doing > so. > > >>> I'm > > >>>>> mainly just saying that we shouldn't say, "nah, can't do it because > > >>> Spark > > >>>>> 2.0 isn't GA yet.") > > >>>> > > >>>> Agree. > > >>>> > > >>>> > > >>>>> > > >>>>> Otherwise, if Zeppelin 0.6.0 is released before Spark 2.0, and we > > >> don't > > >>>>> make Zeppelin 0.6.0 compatible with Spark 2.0, it may be several > > >> months > > >>>>> after the Spark 2.0 release before the next version of Zeppelin is > > >>>>> releasable and supports Spark 2.0. > > >>>> I think releasing Zeppelin as a TLP will be much more easy now :) So > > >>> there > > >>>> is always the possibility to have a minor release with Spark 2.0 > > >> support > > >>> if > > >>>> we don't get it on this one. > > >>>> > > >>>> > > >>>> > > >>>> -- > > >>>> Luciano Resende > > >>>> http://twitter.com/lresende1975 > > >>>> http://lresende.blogspot.com/ > > >> > > > > > >
