On 8/10/07, Jack Schmidt <[EMAIL PROTECTED]> wrote:
>
> To make this effective, one needs to make it easier to have a trac
> account. The development model here is heavily centralized making it
> fairly hard to join in.
It's not hard to get a trac account -- just write to me and I'll
create one
To make this effective, one needs to make it easier to have a trac
account. The development model here is heavily centralized making it
fairly hard to join in.
On Aug 10, 9:25 am, Martin Albrecht <[EMAIL PROTECTED]>
wrote:
> Hi there,
>
> there have been some complaints about the quality of SAG
On Fri, 10 Aug 2007, Martin Albrecht wrote:
>
> On Friday 10 August 2007, David Harvey wrote:
>> Strongly agree.
>>
>> I'd like to add something. I consider "slowness" a bug. When SAGE does
>> something obviously way too slowly, that's almost as bad as a genuine
>> bug. Some slownesses are easy t
On Friday 10 August 2007, David Harvey wrote:
> Strongly agree.
>
> I'd like to add something. I consider "slowness" a bug. When SAGE does
> something obviously way too slowly, that's almost as bad as a genuine
> bug. Some slownesses are easy to fix, some are not.
>
> One of the things that really
On Friday 10 August 2007, David Harvey wrote:
> Strongly agree.
>
> I'd like to add something. I consider "slowness" a bug. When SAGE does
> something obviously way too slowly, that's almost as bad as a genuine
> bug. Some slownesses are easy to fix, some are not.
>
> One of the things that really
Strongly agree.
I'd like to add something. I consider "slowness" a bug. When SAGE does
something obviously way too slowly, that's almost as bad as a genuine
bug. Some slownesses are easy to fix, some are not.
One of the things that really worries me is that someone who doesn't
know the code r
The only thing I would add is that it might be prudent to
automatically add the test cases that trigger bugs to the regression/
unit testing system. That way, SAGE will prevent regressions going
forward. Mathematica has problems where code breaks over and over
again as things are changed.
On Aug
> > 2.) We agree on - lets say - one Sunday a month when we all meet on IRC
> > and sit down fixing those bugs. No new features only bug squashing! Many
> > projects hold events called 'Bug Squashing Party' and this would be our
> > 'party. I.e. we go through the bug reports, assign people, fix th
On 8/10/07, Martin Albrecht <[EMAIL PROTECTED]> wrote:
> there have been some complaints about the quality of SAGE code recently, so
> this is a proposal how to tackle this problem.
Yes!
> 1.) Everybody fills a bug report about _anything_ annoying, wrong, broken in
> SAGE. Everything! Really, ev
