Developer's meeting notes: Google Summer of Code deadlines and mentor sign-up, planning for the next steps in the 2.5 series, bug reporting guidelines, and more updates for the Durian project.
Tom Musgrove writes:
Google Summer of Code
- As you likely heard we've been accepted into the program. Student applications will start be accepted from March 29, 2010 at 19:00:00 (UTC time) to April 9, 2010 at 19:00:00 (UTC time)
- and the ideas list is located: http://wiki.blender.org/index.php/Dev:Ref/GSoC/2010/Ideas
- If you are a core coder and willing to be a mentor or potential mentor please sign up here: http://socghop.appspot.com/gsoc/org/apply_mentor/google/gsoc2010
2.5x next milestone
- Ton had long meeting with Matt about 2.5 planning
- Matt main attention will be with tracker the next weeks, but he'll be more ruthlessly closing reports anything that's not a verified bug can be closed, especially if reporter doesn't respond only reports should be open as todos for our devs, the tracker is not a support system
- Do not report bugs on branches except directly to the developer
- There are two targets we want to make for the betas; one is for 'minimal 2.5 specs' (docs) and one for 'blender stable' (release)
- the 2.5 specs we should be very conservative about, and just move most of it to next series
- the 2.5 UI specs to finish is mostly about thread stuff (render) and multiwin usage and userpref/theme/keymap save and some fishy keymap/operator specs have to be solved, or at least make good guidelines
- the new renderer is giving good performance 'Durian images we render are all full raytraced GI and still within acceptable time'
- Developers please continue helping to fix bugs and to help with the todo list:
- the current artist sprint is showing great results
I have a bug to report. Where do I go?
Why cannot we search in the bugs report? The temporary disable is here for long time now, no? Perhaps it was an other solution?
"Ton had long meeting with Matt about 2.5 planning"
Does anyone else get the feeling that the devs are swamped in work and are struggling to meet the set 2.5 targets? Or is it just my imagination? These guys are working their butts off.
What are the main issues? Has there been unforeseen issues with the design of the 2.5 series? Is it more just about stablizing the API? Documentation?
I'd love to be able to help.
"Durian images we render are all full raytraced GI"
@Socceroos: The main issue is that the last 5% of development (bug squishing, optimization, etc.) generally takes twice as much effort as the total effort spent in the first 95%
I think that Ton has to take major decision about blender 2.5 by himself.
Anyway, I know that Blender is cool and powerful and I've neer been disappointed :)
Good points. I certainly agree that the last 5% requires the most effort.
Like everyone I just visit blender's site nearly everyday to see whats new about our favorite software. Ton and the team are working very hard like all can see. Its been some time now that the Blender team have work on 2.5. I would really like if it was possible to have 2.6 ready by tomorrow :).
But we are just human. What I getting to is, maybe the team should think on getting 2 or 3 days rest and have a good time together. I don't know if you guys also work on weekend. But after a little break I sure all of you would feel refresh!
I'm impatient like everyone to finally have 2.6 underhand. But I'll also be happy to hear that you guys also had a great time together and are all going back home happy after 2.6 is done.
You guys are really just making a great job.
What I do is just download the CSV file and search that.
Pretty amusing post. Couldn’t be written much better. Browsing this post reminds me of my old friend. She always kept talking about this. I will forward this post and I'm pretty sure it will be a good read for 'em. Thanks for sharing!