Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Roadmap to Airavata 1.0
From: Suresh Marru <smarru@apache.org>
In-Reply-To: <521F5012.7010600@iu.edu>
Date: Thu, 29 Aug 2013 09:49:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <83DEA29C-40A2-41D8-A3EC-2EF741B3A985@apache.org>
References: <4A88479A-82F7-479F-BD28-AB4728BBD6F7@apache.org>
 <521F5012.7010600@iu.edu>
To: dev@airavata.apache.org

On Aug 29, 2013, at 9:43 AM, Marlon Pierce <marpierc@iu.edu> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> 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/

>=20
>=20
> Marlon
>=20
>=20
> On 8/29/13 9:39 AM, Suresh Marru wrote:
>> Hi All,
>>=20
>> 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:
>>=20
>> * 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.
>>=20
>> Additional thoughts and tasks we need to accomplish before 1.0?
>>=20
>> Suresh
>>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>=20
> iQEcBAEBAgAGBQJSH1ASAAoJEOEgD2XReDo5h6sH/11h41zkjTyAT4BHo3IVaFe3
> IKB4Z4kZ5LSMnN6OJi/HVm2fEPf10rfFnNUdg3/8lgoWPvqlxkQiaDd0y5w3mfyk
> K/3yhF64Cp8lgirjWBsRvykOsn+U0anmEI8SvegVz6g2hXfwWIQ0D+4bCAOJgzkV
> 0B4SXWwBJYL8K/bbgZopWHvkV1aIvClN5wA2GviblgIuWUaD+b8BycTERipo6GJL
> 7RuUCSRnDOny3qw7Cqh0DMXlXtynjc4myiKo+UeBiq1eGTSQs1Pdf/D7fwKpz3SE
> XjqNtb8C4+8YigGT/v45w2lH1nERGtlJ6rKC5o8BqzMgYqbfe4tKWi2FpRMz9FA=3D
> =3DAeXF
> -----END PGP SIGNATURE-----