You're not a developer are you ?
access is restricted to developers because the bug reports might contain 
personal information.


On Thu, Jan 24, 2008 at 08:43:43PM +0100, MurDoK wrote:
> Hello. Can I also have an account for the bug report system?
> I'm not an expert in tcl but I can handle :)
> 
> 
> Youness Alaoui escribió:
> > Hi,
> > As some of you may have noticed, we just had 34 commits today into SVN. 
> > That's a lot.. and the cause ? the bug report system.. 
> > We just deleted all those old bugs that were already fixed or rare or 
> > whatever. This made the bugs database shrink from 3 GB of bug reports to 
> > 28MB of 
> > bug reports... 
> > What does this mean basically ? well it means that the bug report system 
> > will now be much faster than before since it was VERY slow because it had 
> > to 
> > deal with half a million bug reports, now there are only 3 thousand (for 
> > now). 
> > We (phil, tom and me) fixed many of them so far, but there are still a lot 
> > to look at. Those of you who want to have a look at it and start fixing, 
> > please.. don't hesitate. We have 8 opened 'bugs', and around 1400 'wild bug 
> > reports' (those familiar with the bug report system will know what I mean 
> > by this).
> > For more info, you can always take a look at : 
> > http://www.amsn-project.net/wiki/BugDatabaseGuide
> >
> > If we want to have a 0.97.1 bugfix release, this is the best way to do it.. 
> > in the forums, we had very few people reporting bugs, which means that 
> > 0.97 is VERY stable (compared to 0.95 or 0.96 for which we got the forums 
> > spammed with user reports right after the releases). But if we really want 
> > a 
> > good quality product, this means we will need to have all our users launch 
> > aMSN and use it without ever receiving any 'bug report' from us. That would 
> > mean that the product is stable and that's what we'd like to be aiming at. 
> > To achieve this, we need to close all those bugs from the bug report 
> > system.. some might be 'unfixable', but they still are.. if we see a 'no 
> > disk 
> > space' error, we need to track down down 'puts' and catch them.. this is 
> > the time to make the code more robust.. when we call a function, make sure 
> > the return value is correct (I just fixed some like that, where we did a 
> > [::ChatWindow::For $chatid] and it returned "0" instead of the chat window 
> > path, and added error checking to avoid using the "0" as if it was an 
> > actual window).
> > Anything unfixable should be 'catch'-ed or something else..
> > BUG FIXING TIME IS HERE!!!!!!! 
> >
> > have fun! :D
> >
> > KaKaRoTo
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Amsn-devel mailing list
> > Amsn-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/amsn-devel
> >
> >   
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amsn-devel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Reply via email to