Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of sriksun@hotmail.com designates
 65.55.116.101 as permitted sender)
Message-ID: <BLU179-W414A1BA7A79320DE03C78FA47E0@phx.gbl>
From: Srikanth Sundarrajan <sriksun@hotmail.com>
To: "dev@falcon.incubator.apache.org" <dev@falcon.incubator.apache.org>
Subject: RE: [DISCUSS] falcon 0.5 release
Date: Fri, 21 Mar 2014 03:35:52 +0530
Importance: Normal
In-Reply-To: 
 <CAFfn_RoLigqBic9_EW+OMC+J-_V8=bAtHmL92FZtO=m4cYAw=w@mail.gmail.com>
References: 
 <CAFfn_Rp1H98qS6E+oQRcYOHut6+DUWhgA_PCerKwPe24VELHFw@mail.gmail.com>,<53293295.3080002@nanthrax.net>,<BLU179-W1164EFCAE39E5DC625DDBFA47F0@phx.gbl>,<CAFfn_RoLigqBic9_EW+OMC+J-_V8=bAtHmL92FZtO=m4cYAw=w@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I guess the larger question is do we want to have a multiple release line a=
t different levels of maturity=2C if so what are the best practices here an=
d how can we adopt them. Perhaps we can study some of the projects and figu=
re what works best for us.=0A=
=0A=
There are bug fixes and new features being added simultaneously and there o=
ught to be frequent releases to stable version with bug fixes to help users=
 who use the software in production system. Similarly there may be users wh=
o are waiting on new features=2C but aren't concerned about the stability o=
f the software and are largely in test deployments.=0A=
=0A=
My initial thoughts: We can branch out stable line and make stable releases=
 from this branch and release alpha-versions from trunk. But having more th=
an 2 release lines is going to be quite burdensome. At some point there has=
 got to be enough work done before the old stable line is closed and trunk =
is promoted as the new stable line. Assuming 0.5 is released as alpha=2C be=
fore we add more features there has to be an effort to move 0.5 to beta qua=
lity (let us call this 0.6) and then branch out post 0.6 to have stable rel=
eases out of this (0.6.1). So between 0.5 and 0.6.1 new feature releases ar=
e a burden.=A0=0A=
=0A=
Since we released 0.4=2C we haven't done much to mature the features added =
there and hence the suggestion to defer 0.5. If there is push from the user=
s needing new features added since 0.4 packaged in a release=2C we can proc=
eed with 0.5. But I feel that we ought to mature features that have already=
 been added=A0and have these rolling out in frequent releases=A0to allow us=
ers to use these features in production deployments.=0A=
=0A=
Regards=0A=
Srikanth Sundarrajan=0A=
=0A=
> Date: Thu=2C 20 Mar 2014 09:57:31 -0700=0A=
> Subject: Re: [DISCUSS] falcon 0.5 release=0A=
> From: venkatesh@innerzeal.com=0A=
> To: dev@falcon.incubator.apache.org=0A=
> =0A=
> HCat was not tested with dated sub partitions. Having a fix for these is =
a=0A=
> good idea but there is a dependency on Oozie for this and not sure how th=
is=0A=
> plays out. The retention already has a patch and will review/commit it th=
is=0A=
> week.=0A=
> =0A=
> What else is open wrt stability. There will be bugs and holding off a=0A=
> release calling out experimental features unstable is not a good thing. I=
=0A=
> also wanted to start a discuss thread to explore ideas to see how we can=
=0A=
> make adding new features a breeze and mark 'em as experimental. These=0A=
> features should take couple of release cycles to bake in and will be mark=
ed=0A=
> Beta/GA to be used in production.=0A=
> =0A=
> In that light=2C you could release a 0.4.1 stable version but I can go ah=
ead=0A=
> and make a 0.5 - experimental release with new features for users to play=
=0A=
> with. Lineage is not fully baked. Security for a large part has been test=
ed=0A=
> but can be marked beta.=0A=
> =0A=
> Thoughts?=0A=
> =0A=
> =0A=
> =0A=
> =0A=
> On Wed=2C Mar 19=2C 2014 at 2:30 AM=2C Srikanth Sundarrajan=0A=
> <sriksun@hotmail.com>wrote:=0A=
> =0A=
>> Was seriously contemplating a 0.4.1 stability release over the next 3-4=
=0A=
>> weeks as 0.4 has many bugs particularly with respect to the hcat=0A=
>> replication and retention feature involving multiple partitions. Does it=
=0A=
>> make sense to hold off on 0.5 till End of Apr ?=0A=
>> RegardsSrikanth Sundarrajan=0A=
>>=0A=
>>> Date: Wed=2C 19 Mar 2014 07:00:53 +0100=0A=
>>> From: jb@nanthrax.net=0A=
>>> To: dev@falcon.incubator.apache.org=0A=
>>> Subject: Re: [DISCUSS] falcon 0.5 release=0A=
>>>=0A=
>>> Hi Venkatesh=2C=0A=
>>>=0A=
>>> on my side=2C I should be able to submit new patches proposal soon (nex=
t=0A=
>>> week max).=0A=
>>>=0A=
>>> So=2C no problem for EOM release for me.=0A=
>>>=0A=
>>> Thanks=2C=0A=
>>> Regards=0A=
>>> JB=0A=
>>>=0A=
>>> On 03/19/2014 06:58 AM=2C Seetharam Venkatesh wrote:=0A=
>>>> Hey folks=2C=0A=
>>>>=0A=
>>>> We have made significant progress in falcon with security and lineage=
=0A=
>> apart=0A=
>>>> from the many bug fixes. Should we have a release by EOM?=0A=
>>>>=0A=
>>>=0A=
>>> --=0A=
>>> Jean-Baptiste Onofr=E9=0A=
>>> jbonofre@apache.org=0A=
>>> http://blog.nanthrax.net=0A=
>>> Talend - http://www.talend.com=0A=
>>=0A=
>>=0A=
> =0A=
> =0A=
> =0A=
> -- =0A=
> Regards=2C=0A=
> Venkatesh=0A=
> =0A=
> "Perfection (in design) is achieved not when there is nothing more to add=
=2C=0A=
> but rather when there is nothing more to take away."=0A=
> - Antoine de Saint-Exup=E9ry 		 	   		  =