[Bf-committers] Sunday meeting minutes, 25th feb 2007

[Giuseppe Ghibò]

Ton Roosendaal wrote:
> Hi all,
> 
> Main topic was the need for a 2.43a update or not.
> There were a couple of important fixes in Blender:
> 
> - sculpt: grab bug with shape keys
> - game engine: ray sensor failure
> - composite: vector blur fails on mixed solid+ztransp
> 
> Further the new official book (Blender Basics) could use a stable
> release too.
> 
> On the other hand, we have been fixing such important bugs for over 2
> months, and there is no reason we won't find new such bugs during the
> next days. Freeze has been long enough now (already nicked "ice age").
> 
> Alternative proposal: do a 2.44 in a relative short timeframe, like 2
> months (end of april).
> That gave a lot of positive endorsement.
> 
> So the proposal is:
> 
> - cvs is open again (bcon1)
> - work on new projects can start, but only those that can be completed
> in 6 weeks
>   (please discuss/mention projects in public before starting it!)
> - big refactor projects then can start in may.
> - during next 2 months, also papers/design for refactors can be created
> and approved
> 
> Possible projects for 2.44:
> 
> - make blender 64 bits safe (Ton)
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Sorry, but IMHO this is one of the most important features. Rather than
having it only available at the end of the 2.44 development cycle, can't the
64bit safeness be mandatory before the starting of a new development cycle? In the previous
mails someone said that this would require a week of Ton's "solid work". So
instead of reopening for new features how about fixing the 64bit before? Once
it will be 64bit safe it will also mandatory to keep it 64bit safe during
the development period (could be it either short or long) of adding the new features.

Thanks.
Bye.
Giuseppe.