Hi,

Time based release will be good, and my +1
Firstly of all there must to be planning which features will mapping to
each release in brief level.

and also +1 for Alex idea on nominating a release-manager for each quarter

On Thu, Sep 17, 2015 at 9:44 AM, Nihal Bhagchandani <
nihal_bhagchand...@yahoo.com> wrote:

> Hi Moon,
>
> I think its a good idea to have planned pre-define releases as suggested
> by Vinay.
>
> Nihal
>
>
>
> On Thursday, 17 September 2015 9:23 AM, moon soo Lee <m...@apache.org>
> wrote:
>
>
> Hi Vinay,
>
> Thanks for great suggestion.
> As you know, current roadmap is feature based. But I think it really make
> sense to have regular, time based release policy.
>
> 4 releases/year is very reasonable i think.
>
> While we're in discussion of 0.5.x release, I think we can think changing
> release policy from feature based to time based right after 0.5.x release.
>
> What do you guys think?
>
> Best,
> moon
>
> On Wed, Sep 16, 2015 at 1:39 PM Vinay Shukla <vinayshu...@gmail.com>
> wrote:
>
> Hello,
>
> So far there has been one release of Zeppelin. In the last few months
> there has been much work in the community to add new features and fix
> issues.
>
> It will be great to also have a predictable release schedule for Zeppelin.
> Generally software projects are either time boxed or feature boxed.
> The time boxed releases are very helpful for fast moving projects and to
> help plan.
> For example, the knowledge that a new iPhone version comes out every
> september help people plan their upgrade, or a  train's schedule helps
> passengers plan their trip.
> It will be great to make Zeppelin releases predictable to help the
> Zeppelin community plan their uptake.
>
> So far the current roadmap is feature based. But we don't know when 0.6.0
> will be released.
>
> It would be great to do 4 releases/year for this young project. May I
> request the community to consider releasing 4 releases/year?
>
> Thank you,
>
> Vinay
>
>
>
>


-- 
Cheers,
Madhuka Udantha
http://madhukaudantha.blogspot.com

Reply via email to