[ODE] 0.6 release branch

[Terry L. Triplett]

[If I may chime in as a downstream user rather than a direct contributor
...]

What (if any) release criteria are there to be met?  An alternative approach
to the one you were taking (branch -> stabilize -> release) is to work on
the trunk until a 'releaseable' state is triggered by meeting said criteria,
snapshotting the current state of the trunk by tagging, and releasing.  Set
some new criteria, lather, rinse, repeat.  Maybe it's easier to reach the
ideal of "release early, release often" this way.

Some feedback on the current codebase:

The current 0.6 branch and trunk seem to be reasonably stable, at least on
Gentoo Linux.  The source builds successfully against all permutations of
the current build options, and the tests all run with only a few glitches
here and there (+/- double-precision, +opcode only).

On 4/6/06, J. Perkins <starkos at gmail.com> wrote:
>
> I'm going to go ahead and remove the current 0.6 release branch later
> today. Let me know when you all think we are ready to start moving
> ahead with a new branch.
>
> Jason
>
> _______________________________________________
> ODE mailing list
> ODE at q12.org
> http://q12.org/mailman/listinfo/ode
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://q12.org/pipermail/ode/attachments/20060406/01870f83/attachment.htm