Skip to content
This repository has been archived by the owner on Oct 7, 2020. It is now read-only.

Milestone usage #1280

Open
alanz opened this issue Jun 1, 2019 · 2 comments
Open

Milestone usage #1280

alanz opened this issue Jun 1, 2019 · 2 comments

Comments

@alanz
Copy link
Collaborator

alanz commented Jun 1, 2019

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?

@ghost
Copy link

ghost commented Jun 4, 2019

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)

@fendor
Copy link
Collaborator

fendor commented Jun 4, 2019

This is not the right issue for that.
Please post on #1068

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants