Hello Serge, Michael,


MR>> Well, we could use the process as intended:
MR>> if you attach a fix, mark the issue resolved and the resolution field to
MR>> fixed. If the fix is in the stream, the issue should be closed.
MR>> If the fix is no good, you can always reopen the issue.

SS> The problem is everyone could post a fix, but not everyone could mark
SS> the issue as resolved.

that would mean only people with deep knowledge can post fixes.

I don't assume to know every use of the class I fix, so I can't think
of every side effect my fix might have for other people.

IMHO a fix should be announced here so interested parties can look at
it.

The model you propose (Mantis was intended for) is fine for a small
team of developers not for a community.

"Reopening the issue as the fix was no good" is not what makes people
contribute fixes. Sorry Michael for turning your words but I think
that's how it will be understood.

It's closer to the "If you want it done right you have to do it
yourself" approach than to a community approach.


Regards

Herbert                            mailto:herbertkoenig at gmx.net