The new developer meeting notes are in!
Ton Roosendaal writes:
Hi all,
Here's the notes from a nice short meeting today in irc.freenode.net #blendercoders
1) Blender 2.68 release targets
- Meeting agrees on sticking to planning, which is moving to BCon3 today. There's only three weeks left for doing a next release, which we better spend on stabilizing and a massive bug attack... the amount of tracker reports went close to 150 already.
- Based on the available coders, the following targets were moved:
- Cycles: new hair shaders - including Kajiya-Kay.
- Cycles Ubershader'
- Pie menus
- Save and load "template" blend files
- Multiview and OpenEXR 2.0 migration: suggested is to move that as well, but Dalai Felinto can plea his case still (if he insists :). Brecht van Lommel is available next week for review.
- Updated release target list.
- Python auto-run script becomes "disabled" as default. Proposal for a good UI to handle this will be reviewed this week.
2) Other projects
- GSoC branches for students can be added now. Naming convention will be: soc-2013-name. Where 'name' is descriptive, or name of developer. Student and mentor can decide together on it. Help with adding branches you can ask Sergey, Brecht or Campbell for.
11 Comments
whooo u guys work too fast, amazing, thanx 4 making this possible
over 150 bugs report ? that´s a lot :(
i´ll wait 4 3 weeks until u release 2.68, would b impressive indeed !
thanx a lot
150 Bug Reports is actually kind of a good thing.
Blender definitely isn't bug-free yet (and just as any other program of decent size, probably never quite will be), so 150 reported bugs is 150 bugs known is 150 much quicker works than if the developers had to first find them too.
i got it, thank you kram1032
I would really appreciate it if multiview was not dropped - I should to be running a summer school for 16-18 year olds in about 2 months, and one of the computer rooms we could be assigned has 3D monitors in it - in the event that scheduling allows us to use that room I would love to be able to make use of that! (Obviously there is no point getting it in if its unstable, but if at all possible...)
Don't forget you can get them using graphicall builds if you're/they're feeling brave ;) to be honest I've used them in production... Sometimes I've felt the heat, but the rewards were worth it!
We are unfortunately subject to an IT team - we can tell them which version of Blender to install, and they will do it, but I really don't want to suggest anything other than a stable build. Still, your right that we have the option of downloading it and running it out of a directory (I think - no idea how locked down these machines will be.), but I would much prefer it to be rock solid. We put these kids through an awful lot of pressure, and we really don't want them suffering lost work due to crashes! (Had a kid lose several hours work last year due to some depgraph issue deleting the animation he was creating. Was able to mostly recover it, because he was saving regularly and I had the fileserver backing up every 5 minutes and the bit being edited was saved each time. But you should of seen him whilst I was doing it - he dropped at least a year from his lifespan!)
good point! If you want to try it out anyway, I'm pretty sure that even with locked down machines you should be able to run it...
I look forward to Blender 2.68, most particularly for the Kajiya-Kay hair shader. The "save and load 'template' blend files" is something I haven't heard much of--sounds like just what I've been needing. Good work, guys. And thanks.
Aw, poor pie menus :P
As a part time Blenderhead and full time information security professional, I'm relieved to see the "Python auto-run scripts disabled" by default. I shutter to think of how many malicious .blend files may be floating around the Interwebs. Well done dev team.
any hope for PPC builds ever again?