[ODE] New release?

[Jon Watte (ODE)]

I would rather suggest that, when we want to release a new snapshot, we 
merge whatever has proven to be stable from UNSTABLE into HEAD, and then 
run with HEAD that way for two weeks with ample announcement on the 
list, so that people who might possible be able to test, can do so.

I e, when UNSTABLE seems reasonable stable is a good time to merge it 
over to HEAD and stabilize.

Cheers,

			/ h+


Megan Fox wrote:
>>I agree in theory. I don't know how many people are actually building
>>against unstable (I am, but I not using trimeshes currently), so we
>>might not get any problem reports. I had planned to create unit tests
>>for each issue in the tracker, but obviously that isn't happening fast
>>enough. If you can give me 24 hours I will see if I can free up enough
>>time to write a test. Otherwise, just put it in.
> 
> 
> While I agree that development is good, and that things will likely
> break in the testing process, dead-ifying (I dub this a real word) the
> stable branch has made for a scenario where broken code can find its
> way into an unknowing just-getting-the-latest-code developer's hands.
> 
> Any chance that, before something is committed that is potentially
> death-inducing, someone could throw a post to the list to let us know
> "hey, don't go updating your stable code trees to CVS until we're sure
> this works"?
> 
> --
> -Megan Fox
> http://shalinor.circustent.us/megan/resume/
> 
> _______________________________________________
> ODE mailing list
> ODE at q12.org
> http://q12.org/mailman/listinfo/ode
> 
>