I've been away doing other things for a few days so I haven't been able to
concentrate on the SDO Java release, but now I intend to make it my top
priority. My inclination is to get to the point of having a release
candidate soon, and with a fair wind I would hope that would be by the end
of the week. I've heard of other projects with separable stand-alone
deliverables who post release candidates for a subset of these somewhere
public in advance of the coordinated official release. Could we do this for
SDO? Then people could try it out and we might be able to move from chill
state on the SDO code base a bit earlier than otherwise. I don't know quite
where we would post it. We could just append a "rc<N>" postfix to the name
until such time as we are all ready to cut the full release.
Regards, Kelvin.
On 19/09/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
I'd to checkpoint on where we are for the release, get people's input
on what they are working on and try and pin down when we think we
will be in a position to start cutting binaries. I've summarized
below where I think we are, please fill in the gaps and add anything
that you think needs to be done (or that can be dropped). This is
based on the content mail from Aug 16.
Thanks
--
Jeremy
1) Specs
SNAPSHOTs have been posted to the Apache repo.
Q: are there any changes to SDO pending? Are we happy with the
version there?
2) SCA Kernel (core)
ClassLoading changes: basic hierarchy in place, still need multi-
parent support - Q:is anyone doing this, do we need it?
Integration of databinding framework: complete as an extension,
needs to migrate to kernel which means more tests are needed - Q: who
is doing this?
Async callbacks: assuming this is complete
Complex properties: DOM model for defaults but not values, still
need xpath support and to integrate with databinding framework - Q:
Venkat are you working on this?
Transitive dependency support: first cut repo provided by Meeraj,
need to integrate with hosts, need to add support for using this in
<include> and <implementation.composite>
3) Baseline extensions
idl.wsdl: supported with wsdlLocation, no support yet via
registry - Q: do we need this, if so is anyone working on it?
binding.axis: sync is working, async in progress - Q: Ignacio are
you working on this, what's left?
need to update to a stable version - AXIOM 1.1 is
out, are we ready for Axis2 1.1? is anyone testing this?
binding.celtix: Q - where are we?
binding.rmi: is this working? complete?
databinding.axiom: assuming this is complete
databinding.sdo: is this complete? anything left to do on
TypeHelpers?
databinding.jaxb: where are we?
container.javascript: where are we?
container.spring: where are we?
4) Optional extensions
binding.jsonrpc - in or out?
binding.osgi - in or out?
databinding.xmlbeans - in or out?
databinding.castor - in or out?
container.groovy - in or out?
any other bindings or containers to be in?
5) Host distributions
Standalone - which extensions should be in?
Web - do we still need this now we have the war plugin?
WAR Plugin - do we need web.xml editing?
6) Sample applications
Technology samples - do we have the right ones? are there any we
don't need?
what is the form for these in the release -
bundled as source, separate bundle?
BigBank application - any progress? when will it be ready? do we
hold the release or post it later?
Other areas:
* SDO distribution - are we ready? where are we with samples, doco,
legal review?
* DAS distribution - are we ready? where are we with samples, doco,
legal review?
* SCA distribution - doco? legal?
* Website - are we generally happy with the site? is anyone planning
on working to update the site for M2 content?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
