...
The sage-2.1.0 PR ticket doesn’t make sense, since we want to progress it, but not in this form. It will require meetings and stuff. So what do we do with the card corresponding to the PR?
Dataset longevity doesn’t have an epic, but does have tasks and a project page. When do we make new epics and who can link to/modify them?
Shut down check-ins channel?
To save time in iterations, should we make a “done” label that can be put on issues when they’re ready to advance columns?
Should we make a “required reviewer assignment” column?
JM subdivided the PDB loader task - How should we handle mid-sprint task subdivision?
JW – I approved a PR that was merged before the standup, which caused it to already be in the “closed” column before we talked about it.
How should we handle user issues that come in mid-iteration?