[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epp-dev] Extending Mars Milestones Error Reporting for M3 - new visualizations available
|
To add my 2 cents :
For various reasons the pristine 1.0.0 Sirius build ended up in Mars M2
and not the 1.0.1 we had released in the meantime.
It turned out to be an interesting mistake : the error reporting
actually reported bugs we fixed and released in the meantime, within
those bugs :
- some of them had a criticity which was hard to assess (linked to class
loading and initialization with Equinox), multiples reportings all
leading to the same bug would have helped us to prioritize it.
- others were not detected even with thousands of tests and were only
reported after the final release
In a nutshell : we would have had the error reporting "on" for Luna,
*the 1.0.0 release would have had the level of polishing we could only
achieve with 1.0.1 three months later. Do that for every eclipse project
and we achieve a whole new level of quality for the June release.
I can't see a single reason not to enable this in your package, as a
package maintainer you can use this information if you want to, but if
you don't projects which are interested in getting those reports will
get it then, even if you don't interact yourself with the system.
Cédric
Le 04/11/2014 12:59, Marcel Bruch a écrit :
FWIW,
if you have concerns about automated error reporting, please let me know.
Best,
Marcel
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
