Erik Sandberg writes:
> The reason I haven't added it in, is that I don't fully understand the
> difference between regression and critical.
Yes, maybe you're right. A regression is a reason for a bug to be
(release-) critical.
> So: What is the real difference? When a bug is considered
> regr
[EMAIL PROTECTED] writes:
> The reason I haven't added it in, is that I don't fully understand the
> difference between regression and critical.
>
> Regression tests are, afaicu, important examples that show aspects of what
> lilypond's output should look like. And there is already an official
On Monday 26 April 2004 16.32, Jan Nieuwenhuizen wrote:
> > About priority: I like your suggestion, but I would like to add the
> > current "important" between normal and regression (& I realise that the
> > currently "critical" bugs should be placed there as well). Just so we
> > have two levels o
Erik Sandberg writes:
> My thought with the initial naming was to create something minimal
Yes, minimal is good.
> About priority: I like your suggestion, but I would like to add the current
> "important" between normal and regression (& I realise that the currently
> "critical" bugs should be
On Friday 23 April 2004 11.03, Jan Nieuwenhuizen wrote:
> May I suggest to adopt a bit more bugzilla like naming (eg,
> http://bugzilla.gnome.org/bug_status.html), possibly with adaptation,
> it does not need to be as full blown, ie something like:
>
> priority (high to low): crash/critical, regr
* Werner LEMBERG ([EMAIL PROTECTED]) wrote:
>
> > Finally it's uploaded. All bugs lie in one big directory; this will
> > probably be changed to something better as soon as we can see
> > exactly what we need.
>
> What's the name of this bug-repository? I've missed this somehow.
lily-bugs
i.e.
> Finally it's uploaded. All bugs lie in one big directory; this will
> probably be changed to something better as soon as we can see
> exactly what we need.
What's the name of this bug-repository? I've missed this somehow.
Werner
___
Lilypond-
Erik Sandberg writes:
> Finally it's uploaded.
> I wrote a draft to a readme of how its organised now:
That's grand!
> Properties include:
> crash: The bug causes lilypond to abort with exit code nonzero.
> future: The bug is known and will not be fixed in a near future.
> critical: The bug sho
On Thursday 22 April 2004 07.25, Edward Sanford Sutton, III wrote:
> On Wednesday April 21 2004 14:58, Erik Sandberg wrote:
> > I would however be the only one who
> > actually removes the files from the repository; this because I think it's
> > a good idea that someone always should double-check t
Erik Sandberg wrote:
On Wednesday 21 April 2004 17.47, Mats Bengtsson wrote:
Great!
I suggest to add some information on the procedures also, unless you
want to be the only one to handle these files. If I find a bug, could
I just upload the file to CVS (I have CVS access) or should I send it to
On Wednesday April 21 2004 14:58, Erik Sandberg wrote:
> I would however be the only one who
> actually removes the files from the repository; this because I think it's a
> good idea that someone always should double-check that the bug really was
> fixed.
I hope that unverifiable bugs have a remov
On Wednesday 21 April 2004 17.47, Mats Bengtsson wrote:
> Great!
>
> I suggest to add some information on the procedures also, unless you
> want to be the only one to handle these files. If I find a bug, could
> I just upload the file to CVS (I have CVS access) or should I send it to
> bug-lilypond
Great!
I suggest to add some information on the procedures also, unless you
want to be the only one to handle these files. If I find a bug, could
I just upload the file to CVS (I have CVS access) or should I send it to
bug-lilypond first, or ...?
Same goes for status changes, when somebody with CV
Hi,
Finally it's uploaded. All bugs lie in one big directory; this will probably
be changed to something better as soon as we can see exactly what we need.
I wrote a draft to a readme of how its organised now:
Lilypond Bug Repository
Each bug report should have the following form:
1. Each bug
14 matches
Mail list logo
