I did testing of Gram and GSISSH providers and tested API to run jobs. I found an issue [1] with GSISSH provider but its not a blocker. I rolled back the Jglobus version to 2.0.6 and bouncycastle version to 1.45. I think we are good to create RC2.
Thanks Raminder 1. https://issues.apache.org/jira/browse/AIRAVATA-969 On Dec 18, 2013, at 9:32 AM, Lahiru Gunathilake <[email protected]> wrote: > I have tested the same scenario on my big screen it worked fine, but on my > mac it gave the same issue. > > Regards > Lahiru > > > On Wed, Dec 18, 2013 at 9:26 AM, Chathuri Wimalasena <[email protected]> > wrote: > We encountered [1] while testing. I'm not sure whether this is a blocker or > not. Since it only comes with Mac OS, this may not a blocker. But if you are > a Mac user, you won't be able to run a workflow which has multiple inputs > from xbaya. > > Regards, > Chathuri > > [1] https://issues.apache.org/jira/browse/AIRAVATA-971 > > > On Tue, Dec 17, 2013 at 3:30 PM, Saminda Wijeratne <[email protected]> wrote: > I'm not seeing any blockers so far with the RC1. > > Did the 5/10 min tutorials > Basic descriptor and workflow tests using XBaya > Ran the client samples > Build the source distribution with tests on a clean m2 repo > > Minor issue was reported via JIRA[1]. Updated the source code with the > version 0.11 for XBaya version and Airavata client version. > > If no one else finds any blocker issues I think we can go for an RC2 which > would be the final build for 0.11. wdyt? > > Thanks, > Saminda > > 1. https://issues.apache.org/jira/browse/AIRAVATA-970 > > > > > On Sun, Dec 15, 2013 at 1:28 PM, Lahiru Gunathilake <[email protected]> wrote: > > 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 > > > > > > -- > System Analyst Programmer > PTI Lab > Indiana University
