My hope, as expressed in the original discussion thread [1] which first
explored the possibilities of this change is that  members of the Tuscany
community interested in SDO Java would come to the new project community.
What happens there is then a community decision and a community action
process. The scenario I favour and would encourage would be to focus on the
new reference implementation code base and help community members to migrate
to that. If this involved some level of development of the existing code
base then I can envisage the community creating two implementation
sub-projects in the new project's code base,  one for the RI development,
and one for the existing Tuscany code base.

I can assure you that I don't plan to lose any of the good work done in the
Tuscany SDO CTS work in my focus on developing SDO Java and in particular in
fulfilling the requirements of creating a TCK for JSR 235.

Kelvin

[1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg02487.html


On 28/02/2008, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> kelvin goodson wrote:
> ...
>
> > implicit in this change to the charter is the
> > understanding that if another Apache other project is established with
> an
> > explicit remit for SDO Java development,  then we would work towards
> > ensuring that new  development happened in that new project.
>
>
> OK that helps, Thanks. I have a few more questions:
>
> Would Tuscany contribute its current SDO Java implementation [1] to that
> new project?
>
> Would Tuscany continue to maintain the SDO code that has been delivered
> in several releases?
>
> What about the SDO Java test suite [2]?
>
> What about the Tuscany SDO C++ implementation [3]?
>
> [1] http://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/
> [2] http://svn.apache.org/repos/asf/incubator/tuscany/java/cts/
> [3] http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sdo/
>
>
> --
>
> Jean-Sebastien
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to