On Thu, Jan 29, 2009 at 10:38 AM, ant elder <[email protected]> wrote:
> Back in November we voted to start Tuscany 2.x to create an version of > Tuscany compliant with the new OASIS versions of the SCA specifications (see > [1]) but we've not really discussed any timeframe for that. OASIS are > planning to publish the final versions of the specs along with the > compliance tests around mid 2009, talking to the spec guys they suggest June > or July is looking realistic. > > Wouldn't it be good if Apache Tuscany was one of the first to announce a > release supporting those new specs, so how about using that date to aim for > a final Tuscany 2.0 release? If people agree with doing this then we have > just 4 or 5 months to finish 2.0 so i wonder if we need to be a bit more > organised. > > One thing I thought could help is if we write the 2.0 release notes _now_ > and then we can use that as the high level guide to what we need to get > done. > > Another thing that could help is if we use JIRA more to track most of the > work items so we have one central place showing all the work remaining. We > already have the Java-SCA-2.0-M1 and Java-SCA-2.0 categories in the JIRA > system so how about we now try to create JIRAs for all the bits of work we > know we need to do, using things like the release notes, or the 2.0 themes > thread [2], or the various wiki pages already created for 2.0. > > We'd all need to help with this so we cover all the different areas and we > wouldn't expect to come up with the complete list right away but I think we > could come up with a lot of the big items and once we've done that we'll be > better able to see if we do have a realistic chance of getting it all done > in 4 months. Having the one big JIRA list might also make it easier for > people who want to help out but don't know what they could be doing. > > Is this type of thing worth trying, or any other ideas? WDYT? > > ...ant > > [1] http://apache.markmail.org/message/na5r3ghoji6nqlzw > [2] http://apache.markmail.org/message/xrpzr7pcg5b5h46v > > > All good ideas, more sources of info The incomplete OSOA/OASIS diffs page - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/OSOA+SCA+vs+OASIS+SCA The incomplete conformance tests page - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Conformance+Testing It would seem like a good idea to do a bit of test driven development. We can't claim compliance unless we have the tests anyway. Mike has been beavering away building test but there are a lot of them to do. Creating them will help us understand what has to change. So when creating JIRA for change indentifying which tests demonstrate the change would be useful. Also we have the roadmap page ( http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Java+SCA+Roadmap). Would be great to have JIRA for all the individual items. Release notes is also a good idea. I still feel the need to pull it all together somewhere, e.g having something that holds the JIRA quiries for each Milestone, holds pointers to release notes, spec diffs and test pages etc. Simon
