The latest coding chat can also be found on #blendercoders IRC channel.
For general live dicusions about Blender visit the #blenderchat channel.
News and snippets of information can also be found on Ton Roosendal’s, and #b3d twitter feeds.
I have no news at the moment on 2.6x, I would imagine no one apart from Ton and the key developers do as 2.59 has just been released, but in time it will come, and I think the above links are going to be very good sources of information.
So ladies and gentleman keep your eyes and ears open, and when you do hear news about the 2.6x development, please post in this thread. Links to sources would be good.
Cycles site comes up for me…
on a side, but important, note.
why has this thread been moved…while the other thread was just fine where it was??? I would assume this would fall under “news and discussion” not to mention it’s a bit contradictory to move this and not the 2.5 development thread??? so I am curious why?
Speed improvements are not the primary concern at the moment, development is more focused on integration and user interface. There’s isn’t really a fixed schedule, but this is what I have in mind:
within 6 months: initial version in a blender release, focus on integration, user interface, stability
within 1 year: speed improvements and most important features working, ‘production ready’
within 2 years: roughly support all features on todo in the wiki
That may seem long, but I’m trying to be realistic, I’m only able to spend about 2 days a week on this. As far as speeding up the development goes, I’m not sure what to suggest, we’d need to get more developers involved somehow, lack of feedback is not an issue.
I’m not sure why this was moved either, I would think it’s related to Blender news, but we’ll see how the thread goes.
I’ll try and post every Sunday meeting minutes from this Sunday onwards, or if I don’t then it would be cool if other people could. I found in the 2.5x thread that they weren’t always posted every Sunday.
Here’s a short summary of what was discussed on today’s meeting:
2.59 release, plans for 2.60
Note: tracker up to 206 open reports! No real showstopper reports in
Long discussion on how to manage a ‘freeze’ after release. Some like
to have crucial fixes ported over to the the release-branch, some
prefer a period (week) of commit-only-fixes. Debate can continue over
Agreed is that the short freeze period around release should also
get a formal “unfreeze” notification on this list.
Branches mentioned that could get included for next release:
Joshua Leung’s work on animation system
Benjamin Cook’s work on motion capture input
Joerg Mueller’s audio/speaker work
Will get further reviewed or decided next week.
Note: buildbot now does Win x64 builds too.
BMesh progress; Campbell is ready to work on it, will work on a
planning for it. We have to define when it’s ready for trunk (i.e. how
much can temporarily not work yet).
Google Summer of Code
“Pencils down” soon, we’ll update students with requirements as soon
Google tells more details
I think this is a great thread. News related definitely… oh well the mods had their hands full with the last 2.5 thread. Suppose it makes sense.
Just on the 2.6 topic, has there been any other officially ok’d branches announced for merging into 2.6? In the siggraph interview with 3dtotal Ton mentioned the raytracing branch will get merged, but if Cycles is also to be merged isn’t this a bit of double work? just wondering.
Stable for long term productions, development branch for tests, R&D etcetera.
Having a stable build that gets regular bug fixes would be ideal, features could be merged in every second release, allowing enough time for the long term version to have been thoroughly field tested and debugged before new code, and bugs are introduced.