If we "delete the branch and re-copy it at some later point", then the
release notes and the sandbox page should direct user of the sandbox to
"Fusion". As a non-sandbox user, this is an acceptable option.
A scan of the commit message reveal the following commits since the branch:
TOMAHAWK-258
TOMAHAWK-906
Revision 511613 - http://svn.apache.org/viewvc?view=rev&rev=511613
TOMAHAWK-917
TOMAHAWK-910
TOMAHAWK-921
Although I would prefer the delete option, a speedy release is more
important.
Paul Spencer
Jeff Bischoff wrote:
Depends whether we want the Tomahawk code to be pre-Fusion or not. Of
course Fusion is a separate subproject, so it really only affects the
(deleted) Sandbox components, right?
Wendy Smoak wrote:
On 3/5/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Not necessarily. There was no 1.1.6-SNAPSHOT in JIRA to choose when
closing the issue. I added one and edited the issue. Now it's up to
the releae manager whether to merge that change to the branch.
Hold on... the trunk *is* at 1.1.5-SNAPSHOT:
http://svn.apache.org/repos/asf/myfaces/tomahawk/trunk/pom.xml
And so is the branch:
http://svn.apache.org/repos/asf/myfaces/tomahawk/branches/1_1_5/pom.xml )
That's not allowed. :)
What to do depends on how soon someone has plans to do the Tomahawk
1.1.5 release. Either we
1. update trunk to 1.1.6-SNAPSHOT or
2. delete the branch and re-copy it at some later point
