Thinking....
Description
Description
Event Timeline
Comment Actions
FYI, Developer-Advocacy plan to not use/create monthly Sprint projects anymore in Phab but use a milestone subproject for quarters which is displayed as a column on the workboard of https://phabricator.wikimedia.org/tag/developer-relations/ - we're experimenting. :)
Comment Actions
neat!
/me thinks outloud
So, assuming:
- Release-Engineering-Team were to be more closely trimmed to only include things that we're likely to work on soon (including this current quarter's work).
- I could add Release-Engineering-Team to all tasks that we plan to address in the current/upcoming quarter
- Create a milestone for current and current+1 quarters in Release-Engineering-Team
Then I could move those tasks to their appropriate milestones.
Wins:
- one big overview of what is planned for the current and next quarters (in Release-Engineering-Team's workboard)
- get rid of the eg releng-201516-q4 projects
Loses:
- a new system
- Greg has to keep up with it and triage Release-Engineering-Team more heavily (something I want to do, but right now there's not much of a payoff for it)
Comment Actions
@mmodell was thinking about similar things on IRC today:
greg-g: can I create milestones in releng-201516-q4? seems like a repo migration milestone would make sense (or at least a column)
So, some more preamble thoughts:
- the Release-Engineering-Team board really isn't used by anyone on the team for managing their work (and I don't actively manage it... well... at all), so I don't feel too bad making any big changes
- TPG, VE, and Community Engagement (CLs and DevRelations) are also experimenting with milestones as sub-projects of their team project (see this thread on teampractices@)
- DevRel team board: https://phabricator.wikimedia.org/project/view/33/
- Their Q4 milestone: https://phabricator.wikimedia.org/project/view/1913/
- For them, they find the breakdown by month to be useful
What about for us:
Release-Engineering-Team board be made up of:
| Epics | To Triage (default) | Backlog | Blocked | Watching | FY1516Q4 | FY1617Q1 | FY1617Q2 | FY1617Q3 | FY1617Q4 |
|---|---|---|---|---|---|---|---|---|---|
| For epics | the sorting hat | general backlog of things not yet in a milestone | things we're blocked on (that isn't in a milestone), maybe not useful? | Things we're watching not doing | a milestone | a milestone | a milestone | a milestone | a milestone |
Then, one of those milestones would be:
| Backlog (default) | In-progress | Needs Review | Blocked | Done |
|---|---|---|---|---|
| Things to do that quarter | Things in-progress (with assignees) | Things needing review from non-assignees | Things blocked on others | {{done}} |
All things related to our quarterly goals would go in this milestone. Open question is: do we also include everything else we're working on in here? Is it our quasi-kanban board for things each quarter?
This answers @mmodell's question with a "no", but I wonder if that's OK or if there's something else he'd be missing from the above proposal?
Implementation details:
- I'd probably just create new milestones called, eg #releng-FY1516-Q4 and bulk moving the releng-201516-q4 tasks to them instead of trying to fiddle with the database
Comment Actions
Oh, and this also keeps the project workboards (eg: scap3, ci-infra, etc) alone and they can categorize how they see fit. IOW: this shouldn't mess up already useful workboards like the Scap one.