Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rdf4j-dev] backlog refinement: closing stale issues

I think we should keep any issues that are actual bugs, regardless of if anyone ever intends to fix them. Same for PRs that demonstrate bugs. 

Håvard

On 9 Apr 2021, at 01:14, Jeen Broekstra <jeen@xxxxxxxxxxxx> wrote:


Fwiw I'd also like to do a bit of a cleanup on some of the open pull requests - there's a lot of stale code there with conflicts and build errors, and I want to get to a state where all the open pull requests we have are actually actively worked on (with some leeway on "active" of course, we're all volunteering our time and you can't always plan things fully).

Same with "demonstrates bug" PRs. They can be useful, but not if they just sit there for months on end.

Some PRs can be rebased and continued, others should just be closed and perhaps even their branches removed (that's obviously something we will decide on a case by case basis). 

Cheers,

Jeen

On Thu, 8 Apr 2021, at 20:46, Håvard Ottestad wrote:
That’s great Jeen :)

Håvard

> On 8 Apr 2021, at 03:04, Jeen Broekstra <jeen@xxxxxxxxxxxx> wrote:

> 
> hi all,

> I am planning to spend a little time in the next few days on cleaning up our issue backlog. We have over 300 open issues at the moment, the vast majority of which has not been touched in ages (in quite a few cases issues go back all the way beyond the start of RDF4J, right back to Sesame). 

> While some of these may still be good ideas or bugs that still exist, clearly there is insufficient interest in actually fixing them: nobody comments on them to ask what the status is, and we ourselves just ignore them. They are just gathering dust. Their descriptions tend to be vastly out of date with the current state of the code base as well. 

> I will go through this and quite rigorously close these issues, labeling them as "stale" or "won't fix" as appropriate. I want to get our backlog in a shape where the only issues in it are ones that are still somewhat likely to be addressed in the near to medium future. 

> If an issue I closed in this way turns out to attract renewed interest, we can either re-open, or create a new ticket (as appropriate). It's a good way to measure engagement with what needs prioritizing as well. 

> Cheers,

> Jeen

> _______________________________________________
> rdf4j-dev mailing list
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev
_______________________________________________
rdf4j-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev


_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev

Back to the top