Learn more about these different git repos.
Other Git URLs
I see pagure recently added milestones, and after playing with them a bit, i have a few ideas.
From what i can gather, the milestones are just tags that have been identified in the milestones section in the repo settings. From a user point of view, i found this a little clunky to wrap my head around. FIrst i added a milestone, and then went to try to mark a bug with that milestone, and could not easily find a way to do that.
What if we tweaked the milestones implementation to be a seperate metadata item for an issue or a PR? (rather than a tag). My assumption here is that one PR or Issue will only really apply to a single milestone.
The advantage of the current approach is the possibility to add something to the roadmap without assigning it to a milestone.
Adding a milestone key to a the tickets would mean that there must be a milestone 'future' or so to mark ticket planned on the roadmap but not assigned to a milestone.
Does that make sense?
Hmm, i'm not sure what the difference between a roadmap and a milestone is here.
Typically, milestones are going to be (when they are created) future releasepoints, right?
I am just not sure of the mixing of tags / milestones makes sense to me
Typically, milestones are going to be (when they are created) future release points, right?
Yes, and the idea is to support saying something like "we plan on having this (thus it's on the roadmap) but we do not know when that will be (thus no milestone defined).
I can understand that, I'm just not entirely convinced about changing this for now. Maybe in the future, if more people are impacted or complain :)
Metadata Update from @ryanlerch: - Issue close_status updated to: Won't Fix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.