>> follow no apparent convention =P
> Releng doesn't care if bleeding-edge dev goes in trunk or a new
> branch, it's all the same. That being said, we offer nightly builds
> for a reason... if a potential contributor wants to look at the latest
> and greatest for a specific version, maybe we should start providing
> PSFs again to automate the code checkout process.
Ok... so I vote for the creation of the following structure:
trunk
trunk/as (holds whatever I want... bleeding edge or not so long as I
communicate with jboss tools)
branches
branches/releases
branches/releases/release1
branches/releases/release2
branches/workspace
branches/workspace/ganymede
branches/components/
branches/components/as
branches/components/as/my_jboss_tools_2.1_maintenance_branch
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)
I also vote that the following branches be removed as outdated.
** If any of these branches are still in active use, PLEASE SAY
something! **
> |- before_xulrunner
> |- jbosstools_xulrunner
> |- before-eclipse-3.3
> |- jboss
> |- JBW_BERLIN_2006_BRANCH
> |- REWRITE_2007_16_4
I got no objects to that.
/max