Looking over the tracker, these compositor bugs seem to be the most serious problem.
There's a few other regressions compared to 2.66, but they do not look important enough to let 2.67a wait for them. http://projects.blender.org/tracker/index.php?func=detail&aid=35313&group_id=9&atid=498 http://projects.blender.org/tracker/index.php?func=detail&aid=35321&group_id=9&atid=498 http://projects.blender.org/tracker/index.php?func=detail&aid=35373&group_id=9&atid=498 http://projects.blender.org/tracker/index.php?func=detail&aid=35374&group_id=9&atid=498 http://projects.blender.org/tracker/index.php?func=detail&aid=35388&group_id=9&atid=498 On Thu, May 16, 2013 at 2:54 PM, Campbell Barton <ideasma...@gmail.com> wrote: > We are planning on calling 2.67a ahoy soon within 24hrs, created a tag > and merged fixes from trunk, > However Brecht pointed out there are some compositor bugs (possibly > regressions?) > > http://projects.blender.org/tracker/index.php?func=detail&aid=35386 > http://projects.blender.org/tracker/index.php?func=detail&aid=35380 > http://projects.blender.org/tracker/index.php?func=detail&aid=35369 > > So many changes are going into trunk (fixes and features) but I'd > rather not postone 2.67a too much longer. > But known regression should really be fixed. > > > An updated list of changes in 2.67a is there. > http://wiki.blender.org/index.php/User:Ideasman42/267a_bugfix > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers