-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Looks like a good list. What is the time frame? SC13 and December 31 are two candidate dates to aim for.
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/ iQEcBAEBAgAGBQJSH1ASAAoJEOEgD2XReDo5h6sH/11h41zkjTyAT4BHo3IVaFe3 IKB4Z4kZ5LSMnN6OJi/HVm2fEPf10rfFnNUdg3/8lgoWPvqlxkQiaDd0y5w3mfyk K/3yhF64Cp8lgirjWBsRvykOsn+U0anmEI8SvegVz6g2hXfwWIQ0D+4bCAOJgzkV 0B4SXWwBJYL8K/bbgZopWHvkV1aIvClN5wA2GviblgIuWUaD+b8BycTERipo6GJL 7RuUCSRnDOny3qw7Cqh0DMXlXtynjc4myiKo+UeBiq1eGTSQs1Pdf/D7fwKpz3SE XjqNtb8C4+8YigGT/v45w2lH1nERGtlJ6rKC5o8BqzMgYqbfe4tKWi2FpRMz9FA= =AeXF -----END PGP SIGNATURE-----
