A thousand bugs still feel like an overkill to me, even for a bunch of
committers with good intentions.
How about making it a Google Summer of Code project? Doesn't sound
like an exciting job, but would be extremely useful for the project.
Triaging 10 bugs per day and given 3 months of work, the student
should be able to touch all of them. Maybe even fix trivial ones.
What do you think? In my opinion it's at least worth trying.
Cheers,
Tomek
On Tue, Mar 19, 2013 at 1:35 AM, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
On Tue, Mar 19, 2013 at 1:00 AM, Robin Stocker <robin@xxxxxxxxx> wrote:
Robin Rosenberg wrote:
How about killing some of 'em bugs before introducing a lot of new
ones?
All open: 1080
https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=EGit&product=JGit&query_format=advanced&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&limit=0&list_id=4804075
Removing enhancements still leaves 768 open bugs.
https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=EGit%20sans%20enhancements&list_id=4804082
Yes, we really need to get this list down.
How about meeting up in IRC [1] and try a bug triaging/squashing
"party"? That could speed up situations where we have to make decisions
or need more than one person looking into a bug.
We could create #eclipse-git or #egit, find a date that fits
everyone and see how it goes. What do others think?
Regards,
robinst
[1] http://wiki.eclipse.org/IRC
good idea
--
Matthias
_______________________________________________
egit-dev mailing list
egit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/egit-dev
_______________________________________________
egit-dev mailing list
egit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/egit-dev
