Alex - I agree with you except that so far no-one but me has played with it... 
I thought having it out as an experimental feature might get more people 
involved so we can flesh-out the bugs. 

> On Sep 7, 2015, at 10:04 PM, Alexander Bezzubov <[email protected]> wrote:
> 
> For RInterpreter - as its a great feature and we need to give people some
> time to play with it, and we discuss a minor release right now, so may be
> we should plan it more for 0.6.0?
> 
> As for making a release branch - my only concern that cherriepicking after
> a week may be complicated. May be we can decide right on PR merge if it
> belongs to more then one branch(master, by default and then, need to be
> marked 0.5.x explicitly here and in JIRA, to get in) and our
> tooling(merge_zeppelin_pr.py) supports this workflow too.
> What do you think?
> 
> Other than that - sounds like an awesome plan to me, thank you Moon for
> outlining it!
> 
> --
> Kind regards,
> Alexander
> 
> On Tue, Sep 8, 2015 at 6:18 AM, Amos B. Elberg <[email protected]>
> wrote:
> 
>> Can we get the rinterpreter in?
>> 
>>> On Sep 7, 2015, at 1:17 PM, moon soo Lee <[email protected]> wrote:
>>> 
>>> Looks like we have consensus of having 0.5.x release.
>>> 
>>> Then, how about following steps for the release?
>>> 
>>> 1. Create a release branch.  (That means freeze the code, release branch
>>> only receives bug fix)
>>> 2. Create rc artifacts from the release branch
>>> 3. Test rc artifacts, fix bugs. Vote for release, iterate 2-3
>>> 4. Release
>>> 
>>> Here's some decisions to be made.
>>> 
>>> When we create release branch?
>>> How we create branch?
>>> How do we handle FixVersion tag of JIRA issue?
>>> 
>>> To me, a week later (14/sept), cherry picking master branch to existing
>>> branch "branch-0.5" for creating release branch. And add 0.5.x for
>>> FixVersion for the JIRA issues included in this branch.
>>> 
>>> 
>>> On Sat, Aug 29, 2015 at 10:53 PM Anthony Corbacho <
>>> [email protected]> wrote:
>>> 
>>>> I think its okay to release often minor change (something like 0.5.x).
>>>>> On Aug 30, 2015 1:57 PM, "Alexander Bezzubov" <[email protected]> wrote:
>>>>> 
>>>>> Enthusiastic +1 on soon 0.5.x release!
>>>>> Great job has been done by the whole community indeed.
>>>>> Then we can release 0.6.0 as soon as the scope is there.
>>>>> 
>>>>> On Fri, Aug 28, 2015 at 11:40 PM, Amos B. Elberg <
>> [email protected]>
>>>>> wrote:
>>>>> 
>>>>>> +1 on interim release. There have been so many changes it would be
>>>>> helpful
>>>>>> to have a more stable code base to develop against. Any way R could
>> get
>>>>>> into that as an experimental feature?
>>>>>> 
>>>>>>> On Aug 28, 2015, at 3:03 AM, moon soo Lee <[email protected]> wrote:
>>>>>>> 
>>>>>>> About tracking number downloads
>>>>>>> 
>>>>>>> Currently download button just redirects browser to
>> http://www.apache.org/dyn/closer.cgi/incubator/zeppelin/0.5.0-incubating
>>>>>> .
>>>>>>> Is there any way to get download number from apache.org/dyn?
>>>>>>> Otherwise we need implant some tracking code into the download
>>>> button.
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> moon
>>>>>>> 
>>>>>>>> On Thu, Aug 27, 2015 at 11:59 PM DuyHai Doan <[email protected]>
>>>>>> wrote:
>>>>>>>> 
>>>>>>>> +1 for  the release.
>>>>>>>> 
>>>>>>>> Agree with IT CTO that it would also be interesting to know how many
>>>>>> people
>>>>>>>> are downloading the built version, but I guess we can have the
>>>>> download
>>>>>>>> statistics from Apache repo, don't we ?
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> On Fri, Aug 28, 2015 at 8:48 AM, tog <[email protected]>
>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> While it is important to understand the traction the project has by
>>>>>>>> getting
>>>>>>>>> the number of downloads we have had with the first release, I
>>>> believe
>>>>>> it
>>>>>>>> is
>>>>>>>>> more important to show that the project is progressing well by
>>>>>> providing
>>>>>>>>> new releases.
>>>>>>>>> 
>>>>>>>>> +1 for an intermediate release
>>>>>>>>>> On Aug 28, 2015 6:59 AM, "IT CTO" <[email protected]> wrote:
>>>>>>>>>> 
>>>>>>>>>> I agree a great progress has been made but before we invest time
>>>> in
>>>>>>>>>> releasing do we have a record of how meny people use the released
>>>>>>>> version
>>>>>>>>>> and not build from source?
>>>>>>>>>> 
>>>>>>>>>> בתאריך יום ו׳, 28 באוג׳ 2015, 08:47 מאת moon soo Lee <
>>>>> [email protected]
>>>>>>>>> :
>>>>>>>>>> 
>>>>>>>>>>> Hi,
>>>>>>>>>>> 
>>>>>>>>>>> I'd like to discuss about upcoming release.
>>>>>>>>>>> A lot of improvements have been made since 0.5.0-incubating
>>>>> release.
>>>>>>>>>>> 
>>>>>>>>>>> 4 Interpreters are added (there're more work in progress),
>>>>>>>>>>> security for websocket and rest api are improved,
>>>>>>>>>>> ux improved a lot,
>>>>>>>>>>> more documentation,
>>>>>>>>>>> many bug fixes,
>>>>>>>>>>> and so on
>>>>>>>>>>> 
>>>>>>>>>>> I think improvements are good enough to make a release.
>>>>>>>>>>> 
>>>>>>>>>>> However, next version, 0.6.0 is not completely done according to
>>>>> the
>>>>>>>>>>> roadmap.
>>>> https://cwiki.apache.org/confluence/display/ZEPPELIN/Zeppelin+Roadmap
>>>>> .
>>>>>>>>>>> 
>>>>>>>>>>> So, how about having one more 0.5.x release before 0.6.0?
>>>>>>>>>>> 
>>>>>>>>>>> Thanks,
>>>>>>>>>>> moon
>> 

Reply via email to