[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-pmc] 4.2 Bug Hunt Competition

I think getting a wide range of Eclipse based applications tested on 4.2 is *very* important. So, yes.

I still believe that widening our contributor base is an important theme too.

McQ.

Inactive hide details for "Oberhuber, Martin" ---2012/02/28 12:25:21---Hm…"Oberhuber, Martin" ---2012/02/28 12:25:21---Hm…


From:

"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>

To:

"eclipse-pmc@xxxxxxxxxxx" <eclipse-pmc@xxxxxxxxxxx>, Andrew Overholt <overholt@xxxxxxxxxx>

Date:

2012/02/28 12:25

Subject:

Re: [eclipse-pmc] 4.2 Bug Hunt Competition




Hm…

While getting patches is of course interesting, is this really the main goal to accomplish at the moment ?

As much as I understand things, many of the really important 4.x defects are not really trivial ones to fix (unless there’s many tagged “helpwanted” … I didn’t check). My impression was that the more important thing at the moment is actually _find_ what’s still a problem, no ?

Martin

From: eclipse-pmc-bounces@xxxxxxxxxxx [mailto:eclipse-pmc-bounces@xxxxxxxxxxx] On Behalf Of Mike Wilson
Sent:
Tuesday, February 28, 2012 5:30 PM
To:
Andrew Overholt; eclipse-pmc@xxxxxxxxxxx
Subject:
Re: [eclipse-pmc] 4.2 Bug Hunt Competition

How about "largest # of accepted patches during the contest period"?

I think anything that encourages people to contribute would be awesome. Heck, if <# of accepted patches> > 3, I'd even offer them commit rights. :-)

McQ.

Inactive hide details for Andrew Overholt ---2012/02/28 10:35:51---Hi,Andrew Overholt ---2012/02/28 10:35:51---Hi,


From:

Andrew Overholt <
overholt@xxxxxxxxxx>

To:

mike.milinkovich@xxxxxxxxxxx, eclipse-pmc@xxxxxxxxxxx

Date:

2012/02/28 10:35

Subject:

Re: [eclipse-pmc] 4.2 Bug Hunt Competition





Hi,

> We EMOers were wondering if there was anything the Foundation could do to help
> drive community help for 4.2 QA. E.g. a bug hunt competition where we promote
> and provide some prizes (iPads or the like).

Sounds like a great idea to me!

It might also be a good way to get people involved in various projects
if we can drive participation there with requests for smoke/manual
testing instructions. I'm envisioning something like "Hi, I'm new to
<project x> and want to verify things work perfectly with 4.2. Outside
of running the unit tests, is there a set of steps I can manually run to
verify things are working as expected?"

It's probably also a good idea to keep a wiki page where bug reporters
can list their bugs and maybe a blog entry about what they tested and
found (could be a good substitute for bugs if they can't find any :).

Andrew
_______________________________________________
eclipse-pmc mailing list

eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc


GIF image

GIF image

JPEG image

JPEG image