# How to best deal with backlog of issues?

**URL:** https://discourse.citationstyles.org/t/how-to-best-deal-with-backlog-of-issues/1626
**Category:** CSL Evolution
**Created:** [April 20, 2020, 12:15pm UTC](https://discourse.citationstyles.org/t/how-to-best-deal-with-backlog-of-issues/1626 "2020-04-20T12:15:42Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Denis\_Maier](https://avatars.discourse-cdn.com/v4/letter/d/8491ac/32.png) [@Denis\_Maier](https://discourse.citationstyles.org/u/Denis_Maier)
#### Post date: [April 20, 2020, 12:15pm UTC](https://discourse.citationstyles.org/t/how-to-best-deal-with-backlog-of-issues/1626/1 "2020-04-20T12:15:42Z")

</div>

I have the impression that one thing that prevents us from making progress with CSL development is that there’s a huge backlog of issues. Any ideas how we should deal with that? I’ve been toying around with a new “Next” column [on the board](https://github.com/orgs/citation-style-language/projects/3) to allow for more focused discussions. But I’m not sure if that is really a good approach? What do you think? Or we start “sprint” where we quickly categorize the issues (as proposed [here](https://github.com/citation-style-language/csl-evolution/issues/14#issuecomment-616235295)). Some are probably easy to deal with. Others need more discussion.

Edit: Perhaps we should just move all issues with milestone “CSL 1.2” to the accepted column. There’s been a consensus that they should be implemented, right? Of course, there remain open questions regarding implementation, but that’s a different discussion.)

---

<div class="post-metadata">

### Author: ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)
#### Post date: [April 20, 2020, 1:49pm UTC](https://discourse.citationstyles.org/t/how-to-best-deal-with-backlog-of-issues/1626/2 "2020-04-20T13:49:37Z")

</div>

OK, so we need three buckets: accepted, rejected, not sure.

I’ll rename it to “in progress” or something.
