858

[beginner]

Not a single of my several dozen (it must be that much) bug reports made it into the latest build. That lets me imagine how many other bug reports must lurk around out there. Abandon hope all ye who enter here - Dante. Another famous Italian.

b.

[fwoolz]

Sparx's bug reporting and bug fixing sorely lack the very traceability EA is so good at tracking... Each bug report should be logged in a database, visible to the user community, with a tracking number and corresponding thread (Micro$oft, BTW, does a pretty good job of this with their Visual Studio feedback site) to track comments, suggested workarounds, confirmation, info on fixes, etc. Then, when the next release comes out, the README should list every bug report WITH ITS TITLE AND TRACKING NUMBER that was addressed (= bug fixed) in the release, along with any other fixes. New features should be in a separate section of the README.

[skiwi]

Sparx's bug reporting and bug fixing sorely lack the very traceability EA is so good at tracking... Each bug report should be logged in a database, visible to the user community, with a tracking number and corresponding thread (Micro$oft, BTW, does a pretty good job of this with their Visual Studio feedback site) to track comments, suggested workarounds, confirmation, info on fixes, etc. Then, when the next release comes out, the README should list every bug report WITH ITS TITLE AND TRACKING NUMBER that was addressed (= bug fixed) in the release, along with any other fixes. New features should be in a separate section of the README.

Vote, vote, vote

[skiwi]

See also public bug/feature tracking

[qwerty]

What's the difference of that thread to this one?

q.

[skiwi]

Nothing, just drawing relevant threads together. Making a stronger case!