[Bf-committers] Blender developers meeting, October 5, 2014

2014-10-05 Thread Ton Roosendaal
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

Re: [Bf-committers] Blender developers meeting, October 5, 2014

2014-10-05 Thread Joel Godin
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 wrot

Re: [Bf-committers] Blender developers meeting, October 5, 2014

2014-10-05 Thread Tom M
Triage is 0) Decide if it is a bug or is really a feature request 1) Making sure all of the information needed to reproduce the bug is present (platform, simplified test file, stacktrace, etc.) 2) Attempt to verify the bug 3) Assigning the bug to a developer with the relevant expertise LetterRip

Re: [Bf-committers] Blender developers meeting, October 5, 2014

2014-10-05 Thread Martijn Berger
2.5) Check again if this is not a duplicate. Both this step and assigning will become easier the more you practice. But even just verifying bugs ( trying to redo the bug based on the description ) and then if needed just adding all the missing details is very very helpful. On Mon, Oct 6, 2014 at

Re: [Bf-committers] Blender developers meeting, October 5, 2014

2014-10-06 Thread Joel Godin
Okay thanks, wasn't sure how that was done, but now found the dropdowns. On Monday, October 6, 2014 2:26 AM, Martijn Berger wrote: 2.5) Check again if this is not a duplicate. Both this step and assigning will become easier the more you practice. But even just verifying bugs ( try