The local consensus on #lisp (roughly, lichtblau and me) was that it will do good to have an issue tracker for McCLIM.
I volunteer to set up/help setting up one, as well as semi-regularly look through the issues posted there.
regards, Samium Gromoff
Quoting Samium Gromoff (_deepfire@feelingofgreen.ru):
The local consensus on #lisp (roughly, lichtblau and me) was that it will do good to have an issue tracker for McCLIM.
Well, all bug tracker software stinks and is a hassle to work with.
That said, I have already lost track of the few gtkairo bugs reported recently, so I am in favour of putting them into a bug tracker. Better a bug tracker that gets ignored than mailing list postings that get ignored and forgotten.
I volunteer to set up/help setting up one, as well as semi-regularly look through the issues posted there.
Whoever "owns" the McCLIM project could just ask for trac to be enabled on cl.net. Then you get to put your bug reports into it.
d.
At Sun, 4 Mar 2007 13:38:12 +0100, David Lichteblau wrote:
I volunteer to set up/help setting up one, as well as semi-regularly look through the issues posted there.
Whoever "owns" the McCLIM project could just ask for trac to be enabled on cl.net. Then you get to put your bug reports into it.
Should we outline a policy for bug reports, while we're at it?
Like "bug report must have a CL snippet demonstrating the issue attached, when applicable"?
d.
David Lichteblau david@lichteblau.com writes:
That said, I have already lost track of the few gtkairo bugs reported recently, so I am in favour of putting them into a bug tracker. Better a bug tracker that gets ignored than mailing list postings that get ignored and forgotten.
I concur, I know of a few bugs that I don't have the energy/skill to fix right now, but which really should be documented somewhere.
Whoever "owns" the McCLIM project could just ask for trac to be enabled on cl.net. Then you get to put your bug reports into it.
This sounds like a sensible idea.
Samium Gromoff _deepfire@feelingofgreen.ru writes:
Should we outline a policy for bug reports, while we're at it? Like "bug report must have a CL snippet demonstrating the issue attached, when applicable"?
I don't think this is necessary, most people who try out McCLIM are sufficiently experienced to provide good bug reports.
-
David Lichteblau -
Samium Gromoff -
Troels Henriksen