You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I left a comment in the #contributors channel of the Slack, but I'm going to put it here as well, as I'd like to have a record.
Are the milestones for users, or maintainers? The reason I ask is because:
Users cannot assign to a milestone.
Maintainers assign to milestones to know "when is this release done?"
I could see that changing if we want to use milestones to link to users "here is what is coming next". But even then, we'll likely link to a specific milestone, and, generally speaking, the description text gets lost in:
I don't even miss the description in there, because there's so much else present.
I guess I'm not sure that we need descriptions at all when they refer to a version. We can link to semver.org if they want to understand what is next. And we could end up with a lot of "next bug fix release" entries that make things MORE confusing for users (unless they also note "in the X.Y series", as you note in the issue summary). When we look at closed milestones, these descriptions are also a bit weird as they refer to "next", but they're now closed, because they were either released or abandoned.
I think the version name, by itself, should be enough; beyond that, look at the issues assigned to it.
After some discussion with @froschdesign , I think the main point of contention I have is usage of the word "next". The usage of the words "patch", "minor", and "major" as parentheticals is good as it helps educate users about semver terminology.
Feature Request
Summary
Add descriptions to automatically created milestones to clarify what they are for.
The text was updated successfully, but these errors were encountered: