Re: [hibernate-dev] ORM 3 JIRA tickets
I guess you would still include some features/improvements issues
I'm sure some legitimate things may get caught up in this, but I'd rather try to
clean things up aggressively, then re-open on a case-by-case basis. If there's
something we close that the community feels strongly about, the hope is that they'll
comment on it and bring it to our attention.
Brett Meyer
Red Hat, Hibernate ORM
----- Original Message -----
From: "Hardy Ferentschik" <hardy(a)hibernate.org>
To: "Brett Meyer" <brmeyer(a)redhat.com>
Cc: "Hibernate" <hibernate-dev(a)lists.jboss.org>
Sent: Monday, March 31, 2014 3:40:55 PM
Subject: Re: [hibernate-dev] ORM 3 JIRA tickets
On 31 Jan 2014, at 21:09, Brett Meyer <brmeyer(a)redhat.com> wrote:
Recently, we've been trying to clean up ORM's JIRA tickets.
There are a lot of duplication, stale issues, etc. One thought was pushing all ORM 3
tickets to the "Awaiting Test Case" state and requesting a reproducer on ORM 4
or 5. They would then fall under our policy of automatically rejecting those tickets that
did not receive a test case within 3 months or so.
Sounds like a fair attempt to try to get a grip on all these open issues.
This obviously would not include new features/improvements, anything
assigned to someone, etc.
I guess you would still include some features/improvements issues, since Bug is the
default issue type and some people don’t change the type
even so they describe a feature/improvement. But that might not be important.
—Hardy