[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Approved minutes of Dec 4 Conf-call
SCA LSC Conf-Call, Dec 4, 2008
Agenda:
1. Roll Call
Bryan, DaveB, Anish, Martin, Sanjay
TCs represented: SCA-Policy, SCA-Bindings, SCA-BPEL, SCA-C-C++, SCA-J, SCA-Assembly
2. Scribe Assignment
Sanjay
3. Agenda Bashing
Approved
4. Approval of transcript of Nov 20, 2008
http://lists.oasis-open.org/archives/opencsa-liaison/200811/msg00007.html
Approved
5. OpenCSA Project Management
a> Schedule Review
Sep 15, 2008 - Raise the bar for opening new issues (for all TCs)
Sep 29, 2008 - Incorporate RFC 2119 language
Nov 15, 2008 - Detailed design for testing work
Jan 23, 2009 - Assembly TC to start 1st Public Review (60 day)
Feb 23, 2009 - Other TCs to start 1st Public Review (60 day)
May 31, 2009 - Finish all the work
July 4, 2009 - Submit specs to OASIS for OS vote
SCA-BPEL: Close to resolving the issue for using 2119 language. No work done yet for adding the tags for the conformance statements.
Number of open issues is small (1 or 2). It should be possible to meet the planned schedule.
SCA-C-C++: 2119 related issue has been resolved. CD containing the resolution has not been approved yet.
15 open issues. 6 issues are directly related to revisiting mapping between languages and wsdl - nearing the end of that work. 2 other issues are specific to C-C++. Some dependencies on assembly - related to conversations/long running request-response. Dependency on java for scopes. No anticipated problems in completing the internally driven work by end of Feb. Trickier part is to track dependencies. Testing work is dependent on SCA-Assembly - can start writing test assertions after wsdl mapping stuff is nailed down.
SCA-Policy: Do not have a draft with 2119 language yet. Current plan is to produce a revision by end of Dec.
Number of open issues is down to 4 with proposals (except 1). Testing work depends upon Assembly tc. With the current status and the upcoming F2F in Jan 09 co-located with Assembly TC, meeting the target of Feb 23 for public review seems feasible.
SCA-Bindings: Have 2119 statements for the 3 specs. Haven't done any work on the tags yet (including accepting the sca-assembly's proposal for tags format). Not sure about target date for the tags related work.
26 open issues right now. Actual number may be lower (about 15) since similar issues exist with each one aimed at individual binding specs. At least 3 issues have a very good direction. Likely to meet the Feb 23rd date for PR but there is also a chance of missing that date.
SCA-Assembly: Finished 2119 language incorporation as well as tags related work. Haven't closed the issue yet. Formal CD has not been approved.
Not sure about exactly meeting the Jan 23 date for PR - may miss the date by a week or two. F2F is planned in Jan. Testing work is started but not finished.
Started having testing calls - but no schedule has been identified. Idea was to have concrete test architecture ready before going for PR.
AI for Martin - Get back to LSC with schedule for testing work. Anish plans to put the question on next testing subcommittee’s call.
Eventing spec might bring in new work for Assembly TC and may affect java, c++ and bpel TCs. May also affect policy TC also a little bit.
SCA-J: Impossible to have 2119 language discussion because of pending large number of issues. 58 open issues. Have extended the telecons. But rate of new issues coming hasn't yet slowed down. Premature to talk about 2119. May need to raise the bar even higher e.g. reject issues with no proposals. May also need a virtual f2f
Unless we reprioritize and re-scope, current schedule can not be met. Even if we only focus on caa and c&i, we still may not make the dates. If jee was put
on lower priority that may potentially provide 2 telecons for sca-j tc and may speed up the work to get close to having caa and c&i on schedule.
Anish - Like the idea of deprioritizing jee. Not sure if we should try to get only the caa and c&i out of the door. Would be more comfortable if there were at least 2 c&i specs using the caa. Given that spring spec is not that big, we may want to consider it. May be ok to deprioritize EJB binding spec since there are other binding specs in progress. Other potential idea is - chair cracks the whip and assign issues to people - set deadlines for issue resolutions - CNA issues with no owner, etc.
We have a single schema in a single namespace. It is going to be tricky to stagger the releases
Martin - we do need a discussion on what conformance across specs for the package of sca specs mean? Martin will raise an issue
AI for Dave - to get back to LSC after having a SCA-J TC discussion about the possible schedule
SDO - Trying to get first CD out by end of calendar year. Major issues pending before 2119 discussion happens but SDO may be on a different schedule track. Dependency on the JSR doing 2.1.1 work puts the SDO on a different track.
AI for Bryan - to get back to LSC with anticipated schedule for the SDO TC
All LSC members are urged to discuss the schedule with with the individual TCs they represent.
b> Requirement of 2 compliant implementations
No discussion due to lack of time
c> Any other blocker issues?
No discussion due to lack of time
6. Next conf-call
Dec 11, 2008 - 10 AM Pacific
7. AOB
None
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]