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
