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
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
Hi!
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?
Yes, Fusion affects the sandbox only (if at all).
I think Fusion should not be the reason to hold back a Tomahawk
On 3/5/07, Paul Spencer [EMAIL PROTECTED] wrote:
Was the Tomahawk 1.1.5 branch created to early? I have seen some commits
that are marked in 1.1.5-SNAPSHOT but are not in the 1.1.5 branch.
http://issues.apache.org/jira/browse/TOMAHAWK-917
Not necessarily. There was no 1.1.6-SNAPSHOT in
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
