-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Airavata-281 and Airavata-282 added. They may need to be subtasked.
Marlon On 2/6/12 11:13 AM, Suresh Marru wrote: > On Feb 6, 2012, at 10:05 AM, Marlon Pierce wrote: > > I'd like to see at least simple examples for for-each and provenance. This > seems like the best way to test, provide some quality assurance. >> Hi Marlon, > >> That will be a good way to provide samples and highlight through test cases. >> Please add a JIRA requests, I can work on these samples this week. > >> Suresh > > > Marlon > > > On 2/6/12 10:01 AM, Suresh Marru wrote: >>>> Hi All, >>>> >>>> While we working through release semantics on the 0.2-incubating-snapshot >>>> branch, the trunk moved quite significantly. Great job from every one in >>>> marching ahead. I think we are in a good position for an immediate >>>> 0.3-incubating release. Any thoughts or objections to this plan? >>>> >>>> I see the following feature additions since 0.2 is branched in december: >>>> >>>> * Grid submissions to supercomputers are now working for basic >>>> applications. >>>> * Registry and workflow launching now have cool API's so web interfaces >>>> can be built against. >>>> * User interface have been improved but this looks like work in progress. >>>> * Workflows now have For-Each iterative support, looks like there are open >>>> tickets on this issues, but workable within this week. >>>> * Registry is now persisting state information from workflow launches and >>>> progress >>>> * Workflows have provenance aware capabilities so the execution begins >>>> from the mid workflow where data is available. >>>> >>>> Please add/modify to the list, but I see these are significant >>>> improvements mandating a release. I propose the following release >>>> preparation for 0.3: >>>> * Since there are enough features already call a feature freeze >>>> immediately. >>>> * Wrap up any changes to these features, test document and make a code >>>> freeze by Friday 02/10 >>>> * Make a release over next weekend. >>>> >>>> This plan assumes the current voting 0.2 release goes through. If we find >>>> blockers in 0.2, I still suggest to stick to 0.3 release plan, branch it >>>> and let the trunk move forward. I am getting bothered with trunk advancing >>>> too much without a release. >>>> >>>> Thoughts? >>>> >>>> Cheers, >>>> Suresh= -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPL//bAAoJEEfVXEODPFIDhhQIAJ1t9D1fxz/Pi5rqR+Ty4miR ni9Q1h8aERRzMV/MDpA+ANnIISo0YtymCXePOJQ3NwTEKC1sr03VxtX10lusMn80 w3vwnsdBmr4R4SuDU7XaNyWCoxceQE51EIl+aluh/G9fHJsw8rYfXoJmZRuwj54C E1cg+WJhnxe+eIAG0vtyoq7mfkZUGVTg5+n3Fxun6FkF3zS2foodvu9C9OXM26aa E05HfSMmNerlfuvEP7FsPcljT4iLZ3H2xx2Nm3v2xqpiNE0RT+iPJQ08exYUcpFC ZA0LMkKQoIs+EJiGBKrPGgLvxZQuKTXfHiCtbGoIQE1oMaUo2bpxmTf7pW+4NGI= =GAqH -----END PGP SIGNATURE-----
