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
{{ message }}
This repository has been archived by the owner on Oct 7, 2020. It is now read-only.
At the moment, milestones are used mainly to record what went in to a given monthly release.
And the incomplete issues are assigned en masse to the next milestone when a release is made.
I suspect this monthly issue move a) spams a lot of people b) creates clutter in the issue's history and c) gives a false sense that some meaningful action has been taken.
I think it might be better to not allocate issues to milestones, unless they are actually being worked on, or planned to be worked on. And then the monthly release just tags them with the milestone they end up in.
Opinions?
The text was updated successfully, but these errors were encountered:
Hi, HIE can launch a precompiled package when the next release is released? The compilation and installation time is too too too long. (At my Fedora workstation)
At the moment, milestones are used mainly to record what went in to a given monthly release.
And the incomplete issues are assigned en masse to the next milestone when a release is made.
I suspect this monthly issue move a) spams a lot of people b) creates clutter in the issue's history and c) gives a false sense that some meaningful action has been taken.
I think it might be better to not allocate issues to milestones, unless they are actually being worked on, or planned to be worked on. And then the monthly release just tags them with the milestone they end up in.
Opinions?
The text was updated successfully, but these errors were encountered: