I agree with the no release policy, but sometimes you do have a need for a simple branch. Actually, the proper term
would probably be "shelf" [1]. I've found shelves a great way to get your own space to try new things, without
disrupting the normal development process. Still, I'd imagine that shelves/branches in the sandbox would be the very
rare exception, not the rule.
Don
[1] http://geekswithblogs.net/flanakin/archive/2005/12/02/61929.aspx
James Mitchell wrote:
I agree. Similar to how jakarta commons sandbox specifically disallows
releases, we should probably have the same (sort of) policy in our
sandbox. So without a release, there's not really a need for
tags/branches.
Your thoughts?
--
James Mitchell
On Apr 3, 2006, at 5:40 PM, Don Brown wrote:
I'd like to flatten the sandbox, leaving it up to each project whether
they want tags or branches. For Struts 1.2 and earlier, the sandbox
represented unfinished code relevant to the release, however now, it
is a sandbox for the whole Struts project and not tied to Action 1.
Therefore, I think it shouldn't have the top level trunk/branches/tags
directories, but leave it up to each sandbox project how they want to
structure their directories.
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
