>> Please don't. >> >> Wether you do your new development in a new branch or in head makes >> zero extra work for you - but if trunk becomes inconsistent it gives >> alot of extra work to everyone working across the projects (which >> most of us do) >> > > But it could cause problems *not* to. What if I want to make an > out-of-sync release of just my tools for some higher build drivers? If I > were to make a release, wouldn't it be reasonable for the user to expect > that *that* work is in trunk and not in a branch? eeh no...why ? That component would be "out-of-the-ordinary" as it is now. How many of the components in JBT do you see doing more releases than we do now with JBT (on different drivers ?) > Not that I genuinely see myself as that ambitious, but, one of the > promises was that we'd be able to make out of sync releases, those that > don't time up with the product. If I were to push forward on ganymede > and make a release tomorrow (obviously hypoethetical) and people > downloaded it and wanted to view the code, it's reasonable for them to > expect the newest release on the newest drivers is being done in the > main trunk. > > Or is this a wrong assumption? It is the common assumption, but the same could be said about JBossTools. And my point is that we can have easy checkouts for both scenarios with equal amount of work if we keep jbt in trunk and spinoffs in branches - if we keep trunk in "sync" Note: we could also go the other way and create a jbt-trunk which everyone would work from except you (or other components that want to do spinoff releases) ...but I don't really see the advantage of this added complexity. Note: If we were only doing releaes every year or had alot more people working in N different directions, then sure - we would have to do this. But that is not what we are doing is it ? /max