Definitely detailed testing of the release candidates will be useful as 0.12 will be significantly different from 0.11. Fixing and improving the integration tests (and, as a precursor, demanding better documentation so that you know what to do) is also very important.
Other suggestions for Shameera? Marlon On 2/28/14 2:14 PM, Shameera Rathnayaka wrote: > Hi All, > > Is there anyway that i can participate this release? some task may be, As > this is first release after i got my airavata committership i would like to > help you guys :) > > Thanks, > Shameera. > > > On Sat, Mar 1, 2014 at 12:16 AM, Suresh Marru <[email protected]> wrote: > >> Good point Amila, thats needs to be done too. >> >> Will you have some time before or after the release to change the sample >> gateway to use the API. That will help you critique the API hands-on. >> >> Suresh >> >> On Feb 28, 2014, at 1:41 PM, Amila Jayasekara <[email protected]> >> wrote: >> >>> I assume that integration tests will be modified according to the new >> API and they will be fixed. >>> Thanks >>> Amila >>> >>> >>> On Fri, Feb 28, 2014 at 1:29 PM, Marlon Pierce <[email protected]> wrote: >>> Here is a summary of stuff that is needs to be wrapped up before we have >>> a release candidate. I'm posting this for the record. >>> >>> 1. End to end testing of Registry, Orchestrator, GFAC, and Monitoring: >>> Chathuri and Lahiru are committing here. >>> >>> 2. GFAC Monitoring Info deposited to Registry: Raminder is working on >>> this. This involves GFAC changes but can go in parallel with #1. There >>> is some implementation work to be done and then integration testing. >>> >>> 3. Need to test the Monitoring API implementation. Chathuri will do >>> this. This is dependent on #3. >>> >>> 4. Packaging: need to figure this out for git. Suresh is looking into >> this. >>> >>> Marlon >>> >>> >>> >> >
