On Wed, Apr 29, 2009 at 10:39 AM, Simon Nash <[email protected]> wrote: > Simon Laws wrote: >> >> On Wed, Apr 29, 2009 at 9:39 AM, Simon Nash <[email protected]> wrote: >>> >>> Luciano Resende wrote: >>>> >>>> On Mon, Apr 27, 2009 at 2:35 AM, Simon Laws <[email protected]> >>>> wrote: >>>>>> >>>>>> I'm wondering if we still want to have this release branch just yet >>>>>> now. If we're waiting for the Axis2 release and it looks like that >>>>>> will be at least a couple of weeks and there's still activity going in >>>>>> Tuscany 1.x so maybe we should delete this branch for now and created >>>>>> it again when we know what Axis2 is doing and pick up more of whats >>>>>> been going on in Tuscany 1.x trunk? >>>>>> >>>>>> ...ant >>>>>> >>>>> +1. There do seem to be quite a few 1.x changes and it would seem to >>>>> be easier to just re-take the branch. >>>>> >>>>> Simon >>>>> >>>> +1 on re-taken the build in couple weeks from now. >>>> >>>> >>> The travel sample poms depend on 1.5-SNAPSHOT. As the 1.x branch >>> has now moved on to 1.6-SNAPSHOT, we need this 1.5 branch for use >>> by people building the travel sample. I am checking out the 1.5 >>> branch and building it now to confirm that it works with the >>> travel sample. >>> >>> Simon >>> >>> >>> >> >> But we could easily move the travel sample on to 1.6-SNAPSHOT couldn't we? >> >> Simon >> >> > I think it's not desirable to do this because it means the travel sample > would continue to depend on a SNAPSHOT version of Tuscany even after > 1.5 is released. AIUI, the current SNAPSHOT dependency is there because > of bugs in 1.4 that prevented the travel sample from working. Assuming > that these bugs are fixed in 1.5, the travel sample should move to a 1.5 > dependency when 1.5 is released and should not depend on 1.6-SNAPSHOT. > > Simon >
We could put 1.x trunk back to 1.5-SNAPSHOT for now till we retake a new 1.5 branch. That would probably be less work than keeping the existing 1.5 branch and having to merge in all the trunk changes. ...ant
