Author: sajolida Date: To: The Tails public development discussion list Old-Topics: [Tails-project] GitLab is now in production Subject: [Tails-dev] how to replace "Core Work" views? [was: GitLab is now
intrigeri: > Where to ask questions and report problems
> There are most certainly some rough edges, confusion, and bugs caused
> by this migration, so:
> - If you have questions or trouble with the new *workflow*, please
> either email <tails-dev@???> or [...]
What's the plan to replace "Core Work" views and tickets?
I see that other teams than UX and Technical Writing stopped using them
years ago, though I thought that it was still the somehow standard way
of giving transparency and accountability on the priorities of teams.
I don't mind stopping using them myself if there's no plan for
replacement but I'm curious how other teams track their priorities. It
might be useful to avoid each team reinventing its own wheel and still
give some transparency and accountability.
I guess that we can use Milestones but then, what do you do with tasks
that your team considers important but for which the team is lagging
behind in terms of capacity?
- Using Milestones and postponing them for too long is not great.
- Relying on the Label "Core Work: $TEAM" might make it easier to loose
them from sight.