META: Triage/update backlog, roadmap, and project boards.

Question

Motivation

We've accumulated a bit of operational debt around milestones v0.9.x as a result of conference preparation, resourcing, other priorities, etc. As a result, we've lost some of the gains that were in place when we had a more clearly defined roadmap, milestones, planning board, and dev board.

What you expected to happen:

Here's a working list of items that I feel are worth addressing:

• Closeout hibernate issues more than 3 months old.
• Remove all ddev issues on the project board that are not planned to address in the upcoming week.
• Remove all ddev issues on the sprint planning board that we don't plan on addressing in the next 2-3 weeks.
• Vet all issues in the 1-2 week queues to ensure they have all the requirements we agreed on upon in our community workflow document.
• Utilize this meta-issue as a checklist for any significant sub issues that need to be spun out.

Here are some wishlist items that may or may not be feasible/practical * Attach any issues completed since v0.9.3 to a newly spun out v0.9.4 and tag an official release against that.

There may be other related issues to reference here, including decisions on semantic versioning, packaging/bundling between the CLI/GUI versions, etc. I'll leave them out for now and pull them into the normal workflow.

REMAINING ACTIONS

• [x] Remove all incubate flags and replace w/hibernate
• [x] Remove all issues from all milestones to start with a clean slate
• [x] Stub out milestones to 1.5.0
• [x] Create placeholder issues out to 1.2.0 and assign to proper milestone

该提问来源于开源项目：drud/ddev

Answer 1

I've completed an initial pass of closing out hibernate issues that are either already complete, stale, not reproducible or items we can wait for end-user feedback on before proceeding.