Ok, I'm going to delete branch 1.5, since I think this is confusing. I'll
wait 2 days for any objections.
The branch "jv" was created in 2000 by Jason van Zyl, and seems to not have
ever had any commits. A personal branch (the only one), never used, created
5 years ago but a former committer not currently actively involved. Think
it's ok to delete?
WILL
----- Original Message -----
From: "Daniel L. Rall" <[email protected]>
To: "Velocity Developers List" <[email protected]>
Sent: Thursday, June 30, 2005 1:29 AM
Subject: Re: branching strategy?
On Sat, 2005-06-25 at 23:12 -0700, Will Glass-Husain wrote:
Hi,
Does anyone understand the Velocity branches in svn?
We have a VEL_1_5_BRANCH. What does this mean since there has been no
released 1.5 version. Note that a recent bug contributor has checked
this
out and found an old version of the code. Should we delete this or am I
missing something?
See the comment in the bug report here:
http://issues.apache.org/bugzilla/show_bug.cgi?id=35504
This was probably a stabilization branch, which is completely reasonable
to create before a release is cut (it's a tag which can't be created
before a release is made). I seem to recall some features being slated
for 2.0 rather than 1.5 which were committed to HEAD. Though, if it's
all being dumped into 1.5, I don't see any problem with doing 'svn rm'
-- if something important was in there, it'll always be in Subversion
history, so could be retrieved if necessary.
(I'm offline ATM, so can't verify the diffs between branches, but that
would be my suggested approach for verification.)
There's also a branch "jv" which I don't understand either.
Dunno, perhaps a "Jason van Zyl" branch? What's the date on it, and who
created it? The relevant information should be available from 'svn log
URL_TO_BRANCH'.
---------------------------------------------------------------------
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]
