Blender 2.70 is one step closer now that all developers have gone in to bug fixing mode for the upcoming release.
Ton Roosendaal writes:
Here are the notes from today's meeting in irc.freenode.net, #blendercoders.
1) Upcoming 2.70 release.
- Planning is still the same.
- We moved to BCon4 level today. That means - only bug fixing!
- Sergey Sharybin checks on report for speed regression with threaded updates, will work on that this week.
- Also reported, UI for image window has problems still.
- Release blocker bugs’.
- Tamito Kajiyama worked with Campbell on the Python issue with non-latin fonts. Campbell found it's a bug in 3.3, but fixed in Python 3.4 (not officially released yet). Suggestion is to not release with a new Python now, but provide it as official testbuild instead.
- Martijn Berger would like to see an official testbuild for MSVC 2013 as well.
- Ton Roosendaal: we need a new splash! The 2.6x series was done by either open movie teams, or by teams on invitation (who appointed/invited next teams). Any suggestions for how to handle 2.7x splashes? Do another call on blenderartists.org?
- Test build call will be on wednesday UTC daytime.
- Everyone who's under BF/BI contract will focus on bugfixing the coming week. Sergey will help by ruthlessly assigning everyone their share of reports!
2) Other projects
- Thomas Dinges worked on Cycles standalone last week. He suggested to give Cycles an own git project. Is being reviewed how to handle this efficiently. Brecht van Lommel doesn't think it's needed to remove it from Blender's source tree, there's a way to have both.
- Lukas Toenne reports he completed first stage of compositing code cleanup. It needs to be checked by the current owners of the code (Jeroen Bakker and Monique Dewanchand). Is a topic for after the release.
12 Comments
I like the term 'ruthlessly assisting'. In the past, I tried to do this myself but, alas, ended up losing a few jobs in this nanny state of mine... :-) Or was it because I 'ruthlessly refused' when others tried to 'ruthlessly assist' me? Anyway, I'm sure the spirit of cooperation will prevail as it's always done for the Blender team. Looking forward to 2.7, and MakeHuman 0.8 Alpha, whichever comes first.
Cycles needs a logo, someone accept this challenge! :) Good idea?
I think the term "ruthlessly assisting" is actually also a good one. I tend to ruthlessly assist my PhD students...
I think the splash should at least include some volumetric elements. Perhaps it is a bit early for a Gooseberry contribution.
if cycles becomes a completely stand alone module, it will be more likely to have problems during render. I would hate to have a long render fail just because a packet or two didn't get sent to the other process in time.
You misunderstand. For Blender Users nothing changes. ;)
But Cycles can be compiled as a independent executable, so this is an option for other people, outside of Blender.
so the version in blender will stay nice and tight to the rest of the framework? that's cool :)
Yes, see also here, I tried to clarify this. http://lists.blender.org/pipermail/bf-committers/2014-February/042869.html
Time to relax. :)
@Splash screen: Launch a competition (but allow a week instead of one weekend)!
Great new stuff for Blender! Great work.
But what happened with the cycles Ubershader? Is it possible to put it in as experimental?
Great to see the devs working hard and 2.7 coming soon. Thanks goes out to all Blender developers!
Just an idea for the splash screen, what if you were to change it around slightly so that Blender could show multiple images? You know, have them cycling around, click the arrow to have a look at the next one. IMHO this would be another way to show top/high quality artworks in Blender without any extra advertising or marketing at all. Plus Blender would still look as great as usual.
And on a more personal level, does anyone else feel that having the splash screen say 20-50% bigger would look nicer as you could then see the image more clearly? :)