Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] AERI conclusions after 3 weeks of Mars.1

To share a personal observation based on my error reporting. It has
only been in the last couple of weeks that I have transitioned all my
development from Luna to Mars. I transitioned the first couple of my
active projects to Mars in June/July and the last significant one only
this week. I upgraded to Mars.1 pretty much as soon as it came out and
I have been sending in error reports since Mars.0 came out. Therefore
in the "reporters per week" I imagine I have been consistently there,
but in the number of hours per week on Mars I have gone up
significantly, and in the complexity of my configurations and breadth
of Mars based plug-ins too.

This report is encouraging, AERI is finding more and more issues.

The "reporters per week" or "number [of] problems we see for the first
time" does not seem to be an issue of Mars.0 vs Mars.1. The problem is
if these issues are regressions since Mars.0 or genuinely new errors
that may have always been there. However, I imagine it is going to be
a lot harder to determine automatically the "since" for an automatic
bug report.

To address the regression concern, it would make sense to compare
projects that treated Mars.1 as a bug-fix only release (such as
platform) vs projects that released new versions (such as CDT).

Jonah Graham
Kichwa Coders Ltd.

On 25 October 2015 at 12:39, Torkild Ulvøy Resheim <torkildr@xxxxxxxxx> wrote:
>> 25. okt. 2015 kl. 13.33 skrev Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>:
>> the number of users certainly affect the total number of error reports send to But it should not have such a big effect on the number problems we see for the first time.
> I was suspecting that a wider range of users would test a wider range of components together causing more problems to be discovered.
>> In addition, the number of reporters per week did not change significantly:
> Ah, that’s worrying.
> Best regards,
> Torkild
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top