I think I'm for scenario 2, but I would want to at least one other 1.3.x
release if for nothing else to fix
the ODE dependencies. In my opinion 1.3.3 depends is not build on stable
release versions, and
if we're leaping to the 2.0 trunk it might take a few months to
stabilize it. So I think we'l
Scenario II sounds like the way to go.
To me it's clear that we should focus on the trunk. This thread
http://markmail.org/message/qqkcedclrbfbkvpc sums up the current state of
trunk.
> From: Tammo van Lessen
> Date: Tue, Dec 8, 2009 at 11:22 AM
> Subject: ODE dev-bran
On Tue, Dec 8, 2009 at 8:28 PM, Rafal Rusin wrote:
> I personally think that we should stay with 1.X and drop trunk for
> now. In future, we could
> integrate in smaller steps features from trunk into 1.X, for example
> in versions 1.4, 1.5,...
> Doing so huge leap into 2.0 now will do no good for
I personally think that we should stay with 1.X and drop trunk for
now. In future, we could
integrate in smaller steps features from trunk into 1.X, for example
in versions 1.4, 1.5,...
Doing so huge leap into 2.0 now will do no good for this project,
since recently there is
no much committers doin
Hi ODE devs,
on the IRC channel, we had in interesting discussion yesterday about the
current branch situation and I (have been :)) volunteered to raise this
issue here. Although /trunk has been communicated to be the successor of
the 1.x branch, development still goes on on 1.x so that we basical
