Perhaps drop milestone from issues
I am wondering why we have milestones in issues at all. They seem to be numbers that change every 3 months without any purpose.
- We don't use the number to plan anything afaik.
- We are also not moving release dates due to features with a milestone that are not done yet.
- We don't track progress afaik, or move work when progress isn't fast enough.
So my proposal is
- Don't add a milestone to issues. When the issue is done, it's done.
- Assign yourself when you want to work on something.
- Unassign yuorself when you don't wantt o work on some issue.
- When the issue is done, close it (mostly automated).
- The next release will contain all features that were added in the code.