[Bf-committers] Proposal for 2.36 release

[Ton Roosendaal]

Hi devs,

Looking at the amount of new tracker reports we get in, there's  
evidence we can use another period work on stabilizing the code,  
instead of directly moving to new projects.
Part of the bugs (but not all!) are related to the large amount of  
recoding and new stuff in 2.35, and it also seems that many users now  
not only test, but also actually *use* the release. :-)

As discussed in the sunday meeting, I'd like to propose to extend the  
"CVS freeze" for at least 2 weeks, with only commits allowed based on  
reported or found errors in the code.

For Python, game engine, new deform features, and undo system still  
more than enough issues exist to work on... hopefully we can work on  
that to make a 2.36 'stable' version, and then move on to real new work  
(like the transform refactor, softbodies, work on animation system, UI  
improvements, etc).

We can review current status next week again, and then decide on the  
definite date. But I think 2 weeks is sufficient.

If there's consensis on this topic, I'll post it on blender.org as  
article.

-Ton-

(BTW Bart, doing longer release cycles I don't think would help. I  
think the cycles are too long already... shorter cycles with less new  
features could work better. And of course, set up better communication  
on blender.org on the testing builds, where they are, and what issues  
exactly need a good review.)

------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton at blender.org  
http://www.blender.org