Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [scout-dev] FW: [epp-dev] Extending Mars Milestones Error Reporting for M3 - new visualizations available

if we want to take advantage of this opportunity we need to opt in as quickly as possible. from what I've heard at the democamp in munich from marcel bruch, this option is only available for the mars milestones (ie until mars m7)

-----Original Message-----
From: scout-dev-bounces@xxxxxxxxxxx [mailto:scout-dev-bounces@xxxxxxxxxxx] On Behalf Of Adrian Sacchi
Sent: Mittwoch, 5. November 2014 13:57
To: Mailing list for Eclipse Scout developer discussion
Subject: Re: [scout-dev] FW: [epp-dev] Extending Mars Milestones Error Reporting for M3 - new visualizations available

+1
Sounds promising.

-----Ursprüngliche Nachricht-----
Von: scout-dev-bounces@xxxxxxxxxxx [mailto:scout-dev-bounces@xxxxxxxxxxx] Im Auftrag von Matthias Zimmermann
Gesendet: Mittwoch, 5. November 2014 11:02
An: Mailing list for Eclipse Scout developer discussion
Betreff: [scout-dev] FW: [epp-dev] Extending Mars Milestones Error Reporting for M3 - new visualizations available

i think we should also consider adding the error reporting to the scout epp package. what are your thoughts?

thanks for feedback
matthias

-----Original Message-----
From: epp-dev-bounces@xxxxxxxxxxx [mailto:epp-dev-bounces@xxxxxxxxxxx] On Behalf Of Cédric Brun
Sent: Mittwoch, 5. November 2014 10:38
To: epp-dev@xxxxxxxxxxx
Subject: 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
>

_______________________________________________
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

Attachment: smime.p7s
Description: S/MIME cryptographic signature


Back to the top