Situation summary:

Currently we create a new ticket for each new release cycle, assigning related tasks as subtasks. This works ok, but doesn't result in clear visibly of what remains to complete a release when there is more than a trivial set of tasks. This is particularly apropos with our current big release that includes so many pieces, but I think will continue to be an issue.

I wonder if a Workboard for each release (or series of releases) might be the move? That is what the "Smithsonian" tag is and going to the tag looks like this: https://phabricator.wikimedia.org/tag/smithsonian

In the past this is how I've used Milestones for Issues in Github Projects in the past and found it really helped created clarity and focus, especially towards the end of the release.

I would like to propose we try using a Workboard for at least one release, and then evaluate whether it helped us.

Acceptance criteria:

• We have considered together the visibility of release work, and the pros/cons of the current way we do it.
• We have decided to give a Release Workboard a trial run, or not.
• If we decide to try a Release Workboard, we also:
  • Have considered how to best manage the "Release Checklist", still as its own ticket or to make the component tasks their own independent Phab tickets.
  • Have considered how to integrate this release-centric Workboard into our existing Sprint process.