Well, obviously, we haven't managed the issue list very well, and it got a bit out of control.
I'm in favor of closing them; they've had over a year to sit and gather attention. We have more than enough bugs to keep us busy! I've been trying to close a few myself. On Mon, May 12, 2014 at 10:51 AM, Jochen Kemnade <kemn...@gmail.com> wrote: > Hi, > > on 2013-01-14, in an effort to close some outdated JIRA issues, Uli > added the label bulk-close-candidate to every issue that "has been last > updated more than 1.5 years ago, has no assignee, affects an old version > of Tapestry that is not actively developed anymore, and is therefore > prone to be bulk-closed in the near future". > Also, he asked the reporter to update the issue if it still was ... > well, an issue. > There are 31 issues that haven't been updated since: > > https://bit.ly/1ld7yXJ > or jql: > project = TAP5 AND labels = bulk-close-candidate AND status = Open and > updatedDate < "2013-01-14 15:47" > > I'd say we just close those with another friendly comment. What do you > think? > I guess, we should also repeat this procedure for issues that affect > only versions before 5.3. > > Jochen > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com @hlship
