Hi Chathuri, I think having snapshot as the version in RC is wrong. Every RC has to be like a release and if it pass we just call a vote/discussion thread and do the release. If we do with snapshot and if things go right, then have to change versions and test again. But we can do the release just by changing snapshot without testing but that wrong AFAIT.
I remember doing this mistake in earlier release with RC1 build. I think we can stick to the release management instructions in airavata.org. Regards Lahiru On Fri, Dec 13, 2013 at 3:43 PM, Chathuri Wimalasena <[email protected]>wrote: > Hi All, > > Airavata 0.11 RC1[1] is ready for testing. > > Here are some pointers for testing > > - Verify the fixed issue for this release [2] > - Verify the basic workflow composition/execution/monitoring scenarios > from > - Airavata 5 & 10 min tutorials [3],[4] > - Verify airavata client samples > - Verify the stability with derby & mysql backend databases > - Verify that the XBaya JNLP distribution works > - Verify deploying Airavata server in a tomcat distribution > > Please report any issues[5] if you encounter while testing. Thank you for > your time in validating the release. > > Regards, > Chathuri (On behalf of Airavata PMC) > > [1] https://dist.apache.org/repos/dist/dev/airavata/0.11/RC1/ > [2] > https://issues.apache.org/jira/browse/AIRAVATA-278?jql=project%20%3D%20AIRAVATA%20AND%20fixVersion%20%3D%20%220.11%22%20ORDER%20BY%20status%20DESC%2C%20priority%20DESC > [3] > http://airavata.apache.org/documentation/tutorials/airavata-in-5-minutes.html > [4] > http://airavata.apache.org/documentation/tutorials/airavata-in-10-minutes.html > [5] https://issues.apache.org/jira/browse/AIRAVATA > > > > -- System Analyst Programmer PTI Lab Indiana University
