commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz" <>
Subject Re: [pool] trunk?
Date Tue, 29 Jan 2008 14:44:41 GMT
On Jan 29, 2008 6:51 AM, sebb <> wrote:
> I would prefer to see trunk used for the main development, and
> branches for experimental stuff, but of course this changes over time.
> What is important is that the currently active branch(es) and trunk
> are cleary documented on the web-site and in SVN - I've seen a STATUS
> file used for this, or perhaps a REAME.
> This file needs to be at the top-level of trunk (and the contents
> should indicate that the latest version is always in trunk)
> For a long while in JMeter the trunk was not where the main dev was
> taking place, and this caused quite a few problems (as it was also not
> well documented ...).

Thanks, guys.  Regarding pool, there is no development right now going
on toward the 2.0 stuff, so what makes sense for me is to move the 1.4
code back into trunk and change the pom version to 1.5-SNAPSHOT.  I at
least will be working bugs, responding to issues and looking at the
fairness stuff discussed earlier there, so that makes sense to me.
What I am stuck on is the best way to do it in svn.  Any advice /
suggestions would be appreciated.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message