snip... On Fri, Oct 31, 2008 at 6:28 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:
> Hi, > > I envision that the OSGi enablement will bring a new foundation for the > Tuscany code base with modularity and formalized SPI visibility enforced by > the OSGi within both the development IDE and maven build. > > We are taking a staged approach as I described before and we are making > good progress. I'm not particularly concerned about where the work is being > done. If the community is ready to embrace it (probably when we get into > step 5 and 6), we can move it into trunk. It really depends on how > comfortable we are with the fact that the code will be under construction > for a period of time until it's solid, consistent and clean enough to serve > as a new foundation to build other things on top of it. > > Thanks, > Raymond > > Ok, thanks Raymond, your intention is clear. So, in summary, the code in branch will be proposed as the new trunk when it is ready. It is not the intention to take the lessons learned and apply them to a new trunk bit by bit. Filling in the gaps from other ML discussions (I'm not saying it will be so but I'm painting a picture here). The new (2.x) will be our OASIS SCA code base. The intention being that it will be based on the OSGi foundation from the equinox branch The existing (1.x) trunk is retained, in a branch, as our OSOA SCA code base and is further developed as appropriate. Simon
