Done bug reports, done building, would like to help on Triage and eventually
Patches/reviews (soon as I learn how to use GIT).What is the process for
triage? Just commenting on bugs if you find it is real or not on your platform?
On Sunday, October 5, 2014 11:54 AM, Ton Roosendaal <[email protected]>
wrote:
Hi all,
Here are the notes from today's meeting in irc.freenode.net #blendercoders
1) Release review
- The 2.72 release is now official! We even have a release log on blender.org:
http://www.blender.org/features/2-72/
Special thanks to Marco Ardito!
- Still open to do credit list (I will do), and a readable list of relevant
bugs (for users of 2.71 to know).
2) Targets for 2.72
- The current planning:
http://wiki.blender.org/index.php/Dev:Doc/Projects
- Fracture modifier: has its own branch:
http://git.blender.org/gitweb/gitweb.cgi/blender.git/shortlog/refs/heads/fracture_modifier
- Thomas Dinges reminds everyone about his proposal to make Cycles as default.
He'd need help to finish the missing bits for it.
3) Other projects
- Four of our frequent coders have gathered in the studio of Blender Institute
now.
Read the first report - the discussions on the targets we'll be working on:
http://gooseberry.blender.org/development-targets-for-gooseberry/
- We need more help with patch review and bug tracker triaging... maybe inspire
people via a Development Fund grant?
Thanks,
-Ton-
--------------------------------------------------------
Ton Roosendaal - [email protected] - www.blender.org
Chairman Blender Foundation - Producer Blender Institute
Entrepotdok 57A - 1018AD Amsterdam - The Netherlands
_______________________________________________
Bf-committers mailing list
[email protected]
http://lists.blender.org/mailman/listinfo/bf-committers
_______________________________________________
Bf-committers mailing list
[email protected]
http://lists.blender.org/mailman/listinfo/bf-committers