We've moved into BCon4 (feature freeze, bugfixes only) for Blender 2.63. Release candidates could arrive within two weeks!
Also, the deadline for student submissions for the Google Summer of Code is this Friday!
Ton Roosendaal writes:
Hi all,
Here's the notes of today's meeting!
1) Blender 2.63
- Bugs bugs bugs, ... but still the total went down to 192 (developers closed like a 100 last week!).
- Ton proposes to have a coder blog post about our orphaned code & do a call for new developers to adopt it! We also have to refresh the module teams in general. He'll work with Sergey on it.
- Ton discussed with Joshua Leung to have Francesco & Jeremy (animators Mango) added to the review team for animation features, so they can help deciding to get small & quick fixes in svn.
- Testbuild ahoy! Jens Verwiebe, Nathan Letwory and Sergey Sharybin will use current svn revision to make a build for official testing. Ton will post this as news item on blender.org.
- Planning reminder.
- Proposal: move now to BCon4 (bugfix only) and make it last at least two weeks. Next sunday we can review status (although with Easter many people might have other duties). An official RC build can be done the day after Easter sunday. Final decision on release then happens sunday 15th.
2) Other projects
- Andrea Weikert worked updated the Auto-seam (soc-2011-avocado) branch to latest trunk, to do some work there with the student (shuvro).
- Andrea also started with initial data design for improved data & asset (library) browsing.
3) Google Summer of Code
- Deadline for students: April 6, 19:00 UTC
- We can still use more submissions! Spread the news!
Thanks,
-Ton-
17 Comments
two weeks! tooooooooooo much! come on guys! :D
Sadly 2.62 was ver unstable for me. It keeps crashing when I try to render (not always, but...) and sometimes slows down in edit mode.
Hope 2.63 will be rock solid! Will it also inlude freestyle?
2.63 will probably be even more unstable and maybe slower on mesh editing. All because awesome Bmesh has been added. So get ready to help chasing some nasty bugs!!! And expect 2.63a, b and c along the way! Crazy awesome times ahead...
Where does the negative attitude towards bmesh come from. I have not have reproducable crashes in the 2.6x branch and I have used recent builds quite often. I have had some glitches, where blender is unresponsive for a while when dealing with the vse. But again, not reproducably. What kind of negative experiences have you had?
I have done some modeling in the bmesh branch only because it was a faster method to model and re-topology the same time, its only crashed 2 times one me so it is very stable.
I still would expect maybe 2.63a but not b/c release
If you have a file that crashes when you try to render it, please report it in the bug tracker: http://projects.blender.org/tracker/?func=add&group_id=9&atid=498
For me it works very well. You have to take in mind that you can have un official build binary in a regular folder, and another, svn or unstable for bugs hunting. This prevents to repost bugs already solved. If you experience some problem with the official version, then you reproduce it in the unstable version and if the bug is still there, you can make a report and help to make blender become stable faster.
PD: Don't be away from the project! Everyone can contribute everyday!
crazy times, again, sadly...
Keep on pushing Blenderheads.Love the great work so far.
Can't wait for the test build! Good work lads.
Take all the time you need guys, it still good as it is.
orphaned code! ='( That's so sad!
Followup to the note on orphaned code, Sergey's post is up now: http://code.blender.org/index.php/2012/04/orphaned-areas-help-call/
sorry to push anyone but I do like the first comment of ....COME ON GUYS ...... then again It ought to be, the AMsterdam pace , waiting in utmost kind patient , peace :)
Bmesh is a bit of a issue for me and 62 is sorta unstable in rendering for me two
Too bad we have so many ungrateful whiny users. The program is free for crying out loud so stop complaining!
Help out by reporting bugs if you can't do anything else that's useful.
Take all the time you need developers, great work so far!
Why do they ever make a mess of the manual by disabling the previous blender versions pages and making blabla ...in review ... instead of let it stay until the follow up is in correct state. Bugs aren't just showing up in new functions/options so one is in this very process of bug hunting in desperate need of review what he maybe just had disabled something aka doesn't works anymore or just made a mistake by himself even by accident.