tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (3980)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: Curating Issues
Date Sun, 01 Mar 2015 04:59:07 GMT
Hey Tyler if you want to take a whack, here are some criteria
I tend to use:

1. Bug report from 1+ years old.
  - Close it - either not reproducible, fixed in a later version
and not come back to, or not as bad of a bug anymore since it’s
not a blocker.

2. Feature request from 1+ years old that no one has acted upon.
 - Good candidate for closing - if it was important someone would
have acted up on it.

3. Issue from 1+ years old with lots of discussion on it
  - Poke the issue - see if a consensus can be reached, if not
move forward and close.

4. Issue that is your own that you aren’t interested in anymore
that is 1+ years old
  - Close it you didn’t work on it then, may not get back to it
and no one else has

5. Issue that is 2+ years old
  - Close, regardless, unless it has patch

6. Issue that is 1+ years old, with patch, uncommitted
  - Try to apply patch or minimal effort to bring current with
trunk and apply
  - if too much work ask for help
  - if 1+ weeks and no one replies, close it and move forward

There are more but that’s a start. I’ll check out this article
thanks for sending it.


Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

-----Original Message-----
From: Tyler Palsulich <tpalsulich@gmail.com>
Reply-To: "dev@tika.apache.org" <dev@tika.apache.org>
Date: Saturday, February 28, 2015 at 8:53 PM
To: "dev@tika.apache.org" <dev@tika.apache.org>
Subject: Curating Issues

>Hi Folks,
>I just read an article [0] about managing a large project's issues list.
>Tika currently has 331 open issues. Do we know if all of these have been
>"triaged"? At what point do we want to label an issue as stale and close
>off? What is our preferred split between when to make an issue and when to
>send a message to the mailing list?
>Have a good weekend,
>[0] http://words.steveklabnik.com/how-to-be-an-open-source-gardener?r=1

View raw message