kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #44053
Re: GitLab milestone cleanup
In general, wishlist items should only be given a milestone if they are
either:
1) Actively being worked on by a developer
2) Currently on the plan for the release they are milestoned against (this
one doesn't need a developer assigned/working on them yet)
Other wishlist items don't get a milestone attached to them. I don't think
there is a need to have a "future" milestone though, since the GitLab
interface makes it easy to look through issues with no milestone and the
wishlist label (it is far easier than Launchpad was).
-Ian
On Fri, Jun 26, 2020 at 10:09 AM Eeli Kaikkonen <eeli.kaikkonen@xxxxxxxxx>
wrote:
>
>
> On Fri, Jun 26, 2020 at 8:46 AM Nick Østergaard <oe.nick@xxxxxxxxx> wrote:
>
>> What about feature requests / wishes from users that are very unlikely to
>> realise quickly? Should they still be assigned the new milestone?
>>
>> I just worry they may clutter the overview too much, but I guess when we
>> will see how it goes. :) My concern may not be a real problem afterall.
>>
>> Nick
>>
>>
> Could there be a milestone "Future" for features which are wanted but not
> planned for the next release? For example, some things were in the v6
> roadmap but were moved to the future roadmap, and even more can(?) be moved
> later. It would be better to have them in Future milestone than keep them
> in v6 milestone or remove the milestone completely.
>
> Eeli Kaikkonen
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References