| Re: [stp-dev] SVN Structure |
| Hi Oisin, So I created the bug 25495 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=215495) for this, I raised it agains the website as didn't know other alternative and left the default values for assigned-to which means you :) This is because I wasn't sure who can actually do this (perhaps Adrian S?). Regarding the delivery process, I agree with your proposal of having individual mini update sites, although I'm not an expert in this (yet). Not sure however if this implies any difficulties when there are dependencies between components in STP? (I suppose they can be resolved by selecting all update sites from STP and letting the update manager do its magic). Cheers, Adrian. --------------- Adrian Mos ObjectWeb Project SOA Technical Lead +33 4 76 61 54 02 INRIA Rhone-Alpes 655 avenue de l'Europe - Montbonnot 38 334 Saint Ismier Cedex France On Jan 16, 2008, at 3:35 PM, Oisin Hurley wrote: I am much in favour of not duplicating any work and I think that the sooner we move to the new structure, the better, in order to avoid changes later on. This is particularly relevant for our upcoming commit of plugins to the STP-IM repository where everything has been thought of with the new structure in mind. So my question is, can we go ahead now with the new structure or must we go with the old structure and change it at a later date? Suppose we go with the new structure on a project-by-project basis, would this impact the build system and if so, how much? If there's some tweaking to be done for the projects following the new structure, I would rather do that than change our code structure to be in line with the old layout (and then change it again later :) ).Oisin, what is your take on this? Is this doable or would it entail too many complications on the STP/Ganymede release plan? |