Projects & Workflow

There are two types of projects:

• Things we plan and track for next release.
• Things we plan and track for some eventual release.

The first category encompasses two projects that both work pretty much the same way.

• When an issue is created, a card is added to the project under the "Requested" or "Reported" column.
• Once we know we want to implement it, we move the card to the "Planned" column.
• When we decide what we want to ship for next release, we move the cards to the "Planned for next release" column. Discussion should happen in the VBA Rubberducking SE chat.
• When a contributor decides they want to fix an issue, they move the corresponding card to the "Assigned / In Progress" column.
• When a PR is merged, the cards move to the "Merged" column.
• When a tag/release is created, the "Merged" cards move to the "Released in {version}" column, for future reference.

Features

The Features project tracks issues about requested features and functionality - for example when someone creates a new issue for an inspection they would like us to implement, we'll create a card in that project to track the issue.

BugSlayer

The BugSlayer project tracks issues about reported bugs and other things that don't work the way they were intended to work.

---

The second category tracks progress for a variable number of mid-to-long-term projects. When an important feature requires more work than can be reasonably tracked with a single issue / card in the features project, a project board dedicated to that feature can be created to make it easier to track work and facilitate collaboration.

These projects have a "classical" set of columns:

• TODO
• In Progress
• Done

Contributors are welcome to create issues as they see fit, to make it easier to track these mid-to-long-term projects.