Cita:
Hi all. Here my ideas on the current plans and roadmap:
-2.5x. We are currently preparing the first oficial (non-beta) 2.5x release, numbered as 2.57. This might be released early april. Work Will then continúe 2 months on wrapping up the crucial 2.5 targets, resulting in a may/june final reléase (2.5.
New development: 2.6x.
In april/may we can review with all branch/patch developers status of their work, and make a migration schedule for all new features. This includes projects like GI rendering (Sintel), new Mesh editing, Paint/Sculpt improvements, rigid body physics, new curve/nurbs system. Combining this with a redesign of shader/light system, open cl compositing, a posible VFX based open movie, and all the new Google summer code projects, itll become a massive amount of upgrades again.
Proposal is todo do this in a series of small steps, with stablest branches first. We can call it the 2.6 series resulting in a number of releases named 2.60, 2.61, 2.62 and so on. Each reléase Will be mostly stable, but include new functionality todo be tested as well. Ui and general design specifications for Blender Will remain on 2.5 compatible level.
A related target or Blender remains todo kep improving apis or modules, todo enable larger groups of developers todo work in parallel on projects.
Long-long term.
We should kep doing these upgrades for as long as neded, and - Similar todo during the 2.4 period - Separate out the really big issues todo solver in a bigger Project again, like a Blender 3.0 Project, which could be something for 2015 or later Even.
Weve ben in some kind of freeze long enough now. Let have fun for a while, and then try todo fix it all up again.
Ton-.
