Hi All, With GIT migration and thrift based Airavata API nicely shaping up, how about we target 1.0 release by Apache Con NA 2014?
I wanted to create a JIRA to track all pending tasks we listed, and co-incidentally noticed it marks the 1000th issue of Airavata :) https://issues.apache.org/jira/browse/AIRAVATA-1000 Suresh On Nov 7, 2013, at 2:09 PM, Suresh Marru <[email protected]> wrote: > Looks like we are making good progress and there is lot of active > development, but we will have to miss this deadline we set for ourselves. > Instead of throwing another date, I will create a JIRA story and start > linking major tasks so we can come up with a more informed timeline. > > Any objections to deferring the 1.0 release to some time early next year? > > Suresh > > On Aug 29, 2013, at 9:59 AM, Marlon Pierce <[email protected]> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I'm +1 for setting SC13 as a goal. It is a big opportunity since this >> is when the e-science and cyberinfrastructure community will all be >> together. >> >> But let's hear from everybody. Is Airavata 1.0 by SC13 achievable? >> >> >> Marlon >> >> >> On 8/29/13 9:49 AM, Suresh Marru wrote: >>> On Aug 29, 2013, at 9:43 AM, Marlon Pierce <[email protected]> >>> wrote: >>> >>> Looks like a good list. What is the time frame? SC13 and December >>> 31 are two candidate dates to aim for. >>> >>>> I like both these dates. How about we target SC 13 [1] , i.e. >>>> November 15th for a 1.0 release? and before end of year for >>>> working with various users in upgrading to 1.0 version. That we >>>> enter the new year, freshly returned from holidays with a target >>>> for Airavata 2.0. >>> >>>> Suresh [1] - http://sc13.supercomputing.org/ >>> >>> >>> >>> Marlon >>> >>> >>> On 8/29/13 9:39 AM, Suresh Marru wrote: >>>>>> Hi All, >>>>>> >>>>>> In the last 2 years Airavata has evolved significantly and I >>>>>> feel we are about the time to stabilize the Airavata Access >>>>>> Layer through a API and make a 1.0 release. Here are some >>>>>> thoughts on what we need to do before Airavata can be 1.0: >>>>>> >>>>>> * Ready to move into semantic versioning of releases * Have a >>>>>> API which will survive through minor releases and only calls >>>>>> out for API changes for major releases * Decide upon a going >>>>>> forward SCM among SVN or GIT * Have well documented client >>>>>> integration examples * Scrub of any unused dependencies and >>>>>> revisit the latest versions of critical dependencies * Agree >>>>>> upon supported features * Remove any third party maven repos >>>>>> (down to 1 as of today) * Resolve all the issues which are >>>>>> bugs (and preferably improvements as well) * Revisit all wish >>>>>> style issues and comment on the ones planned to be addressed >>>>>> in near future. * External review of the project by >>>>>> soliciting developers from fellow apache projects. >>>>>> >>>>>> Additional thoughts and tasks we need to accomplish before >>>>>> 1.0? >>>>>> >>>>>> Suresh >>>>>> >>> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG/MacGPG2 v2.0.18 (Darwin) >> Comment: GPGTools - http://gpgtools.org >> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ >> >> iQEcBAEBAgAGBQJSH1OwAAoJEOEgD2XReDo5uqgH/2HlGW1/i2ZQsC6a6SVmoqox >> zcqwooLMwwDuaQvI1w3oZVFdcwNi5SBnRvazDwJY+iqvo1avxZ43EjBhSzrUk1hZ >> zi6CntUG0wLS9sx8nbueoY05faV1+wJRJ5aRsyNfft6MOEdZQA0/rxM94hO5w71N >> joqq6dZ2A1igmWKUB9WenGsIh96UV+pmO8wGFi9swy86DmczJcwyF8txpxmJxNIg >> dwdTmFR6Gi8WQ2SZc3MHrMu8HByjwlKIH6Zv23R/TfVvieIenpd6tK6ZEuHH8ajI >> D08T6AJKGsd4aR/KAU75rwo25hBFg1lA+wy8E7+N+pI5NdEz5Cx3dNkU4qI2Pw8= >> =2KyM >> -----END PGP SIGNATURE----- >
