[Bf-committers] Meeting minutes feb 9 2003

[Ton Roosendaal]

Hi All,

For the 2.26 release, here the list of pending action points and  
planning. Committing to the bf-blender tree is now strictly prohibited,  
except for issues described below:

TODAY:

- everyone: use the blender/release_226.txt to add your release notes,  
what you worked at, etc. (In the future this should become a regular  
habit to do with the file blender/changelog)

- aphex: he will add a notice() text, to warn people the game engine  
doesnt work

- phase: he commits a 2.26 splash screen for blender

- larstiq/sirdude: they will TAG the cvs repository, to mark the release

- all platform managers: compile a release-blender (no debug symbols),  
test it for fitness, and make the release file itself. Even when the  
splash is not in yet, then you're ready for the final step!

- all platform managers: check on library dependencies... especially  
the audio. OpenAL can be compiled in minimal mode. Prefarably, link as  
much as possible with static libraries.

TODAY/TOMORROW (after tagging!)

- all platform managers: compile the final release-blender. Put it  
somewhere at the web where I can download it, mail me the link. I  
cannot receive mails larger than 1 Mb!

- Larstiq: he creates the source tgz tarball.

- Ton/Timothy: they prepare the release text for at the site, upload  
them, etc

TOMORROW/TUESDAY

- when all versions are compiled and uploaded to the site, we do the  
actual release... :-)
   if some version is later than tuesday, it will just be added later.

- check and file bug reports at the projects.blender.org site!

- everyone: don't post this at slashdot, our poor server is already  
having troubles!!! And besides that, this release is a beta, meant for  
testing and meant as a fresh new start.

Good luck!

-Ton-


------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton@blender.org