On 11/12/2024 12:29, Elliotte Rusty Harold wrote:
On Tue, Dec 10, 2024 at 5:10 PM Slawomir Jaranowski
<s.jaranow...@gmail.com> wrote:
On Tue, 10 Dec 2024 at 17:42, Sylwester Lachiewicz
<slachiew...@gmail.com> wrote:
Michale proposed closing all issues that have not been active for more
than 3 years, so there will be less to maintain/migrate.
Maybe we can limit the age during import.
Maybe we should make a decision for each project.
-10
When this was last proposed 5 years ago, I went through Jira and made
sure that every issue older than the cutoff date had some sort of
recent activity so nothing was eligible for automatic closure. I'd
rather not have to hack the process like this again. I routinely find
and sometimes fix bugs that go back to the oldest ones in JIra. If
more devs spent more time triaging old bugs, they'd find more too.
I agree with this! From a reporter point-of-view, it is extremely
demotivating to see a report that you wrote getting ignored for a couple
of years only to be closed for "administration reasons". Don't do this.
It made me stop contributing (by reporting issues) to a few projects
already, because they basically didn't seem to care.
I'd also like to encourage people to deliberately close bugs that are
in fact invalid, unwise, or already fixed. Surprisingly often I find a
final comment from an active committer or PMC member that lays out in
detail how the bug has been addressed or why it shouldn't be
addressed, but they have not pressed the button to close the bug.
Please press the button. However, this needs to be done issue by
issue, not as a bulk close of all issues older than some arbitrary
date.
Rather do this. If we are sure something is not a bug, take the time to
explain it and then close it. If the reporter thinks we're wrong, they
can always re-open. Closing an issue with solid reasoning is much better
than closing it because it was opened more than X years ago.
Maarten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
