All bugs I tagged as show-stoppers have either been closed or fixed, IMHO we can do an RC now.
On Wed, Apr 18, 2012 at 12:12 AM, Brecht Van Lommel <[email protected]> wrote: > Please report issues in the bug tracker if you find them and can give > us steps to redo and investigate the problem. We can't efficiently > follow up on and keep track of bugs if they are reported here. > > Brecht. > > On Tue, Apr 17, 2012 at 12:26 PM, Knapp <[email protected]> wrote: >> I wanted to report this to you. I have been having problems for some time >> with things failing but only when blender has been run. For example Pulse >> audio will go all staticy and need to be restarted. My guess is that >> blender has a memory leak or is writing outside of its data area. So just a >> heads up. I really could not say for sure that it is blender but it only >> happens with blender running. There are also sometimes other problems like >> the graphics not working on other programs when blender has been run. >> 4GB ram kubuntu 11.04 (just upgraded to 12.04 and have not seen the problem >> YET, but have not done much yet with blender.) >> Nvidia graphics 8600 gt 512 mb video ram nvidia driver 295.40 (currently >> but might have been older before). >> >> On Tue, Apr 17, 2012 at 11:09 AM, Campbell Barton >> <[email protected]>wrote: >> >>> Since my initial post we're down from 9 to 3 show-stopper bugs without >>> any new ones reported today, so may make it in 1 week after all :) >>> >>> On Mon, Apr 16, 2012 at 10:17 PM, Campbell Barton <[email protected]> >>> wrote: >>> > Today I went over the tracker and all BMESH_TODO comments in code, >>> > >>> > For now there are 9 bugs I consider show stoppers. All show-stoppers >>> > have highest priority, heres the URL to show them first in the >>> > tracker. >>> > >>> > >>> http://projects.blender.org/tracker/index.php?group_id=9&atid=498&power_query=1&query_id=518&run=Power+Query >>> > >>> > Other devs are of course free to set bugs as show-stoppers (priority 5). >>> > >>> > ------ >>> > >>> > >>> > * Suspect there are others unreported (split by material and xsort >>> > vertex for example were known TODO's in code but not reported). >>> > >>> > * Estimate 1 - 2 weeks to fix - taking into account time to fix some >>> > more show-stopper reports we will likely get. >>> > >>> > * Minimum fix all these bugs before release (IMHO - though if it turns >>> > out some are very difficult we could document as regressions) >>> > >>> > * There are some smaller regressions I don't consider show-stoppers >>> > but should still be fixed or documented before release (xsort vertex >>> > is one example). >>> > >>> > I'll focus on show-stoppers over the next few weeks, would be great if >>> > other devs can look into these issues too. >>> > >>> > -- >>> > - Campbell >>> >>> >>> >>> -- >>> - Campbell >>> _______________________________________________ >>> Bf-committers mailing list >>> [email protected] >>> http://lists.blender.org/mailman/listinfo/bf-committers >>> >> >> >> >> -- >> Douglas E Knapp >> >> Creative Commons Film Group, Helping people make open source movies >> with open source software! >> http://douglas.bespin.org/CommonsFilmGroup/phpBB3/index.php >> >> Massage in Gelsenkirchen-Buer: >> http://douglas.bespin.org/tcm/ztab1.htm >> Please link to me and trade links with me! >> >> Open Source Sci-Fi mmoRPG Game project. >> http://sf-journey-creations.wikispot.org/Front_Page >> http://code.google.com/p/perspectiveproject/ >> _______________________________________________ >> Bf-committers mailing list >> [email protected] >> http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
