[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC] Use GitLab Milestones
From: |
Jonas Hahnfeld |
Subject: |
Re: [RFC] Use GitLab Milestones |
Date: |
Tue, 23 Jun 2020 22:25:57 +0200 |
User-agent: |
Evolution 3.36.3 |
Am Dienstag, den 23.06.2020, 14:11 -0600 schrieb Carl Sorensen:
> On Tue, Jun 23, 2020 at 2:04 PM Jonas Hahnfeld <hahnjo@hahnjo.de> wrote:
> > Am Dienstag, den 23.06.2020, 20:54 +0200 schrieb Jean Abou Samra:
> > > Hi,
>
> <snip>
> > > Actually, I think the while Status family of scoped labels will no longer
> > > need to exist. Status::Fixed and Status::Verified are replaced as above.
> > > In addition, assigning issues should replace Status::Started (this
> > > provides
> > > an additional piece information, the person who started working).
> > > Status::Duplicate
> > > and Status::Invalid should be moved to Type (we already have a
> > > Type::Invalid). One
> > > remaining question is about the difference between Status::New and
> > > Status::Accepted.
> > > I don't really know what should be done about it.
> >
> > Never understood the difference between Started and Accepted either.
> > But removing them requires a bit more thought than that.
> >
> > Jonas
> >
>
> From the Contributors' Guide:
>
> Open issues:
>
> New: the item was added by a non-member, despite numerous warnings not
> to do this. Should be reviewed by a member of the Bug Squad.
I knew that description and, honestly, that would be a show stopper for
me reporting any issue to a project in 2020.
> Accepted: the Bug Squad added it, or reviewed the item.
> Started: a contributor is working on a fix. Owner should change to be
> this contributor.
>
> Closed issues:
>
> Invalid: issue should not have been added in the current state.
> Duplicate: issue already exists in the tracker.
> Fixed: a contributor claims to have fixed the bug. The Bug Squad
> should check the fix with the next official binary release (not by
> compiling the source from git). Owner should be set to that
> contributor.
> Verified: Bug Squad has confirmed that the issue is closed. This means
> that nobody should ever need look at the report again – if there is
> any information in the issue that should be kept, open a new issue for
> that info.
Which one of those would apply to an issue like
https://gitlab.com/lilypond/lilypond/-/issues/6000 ?
Jonas
>
> HTH,
>
> Carl
>
signature.asc
Description: This is a digitally signed message part
- Re: [RFC] Use GitLab Milestones, (continued)
Re: [RFC] Use GitLab Milestones, Valentin Villenave, 2020/06/23
- Re: [RFC] Use GitLab Milestones, Jonas Hahnfeld, 2020/06/23
- Re: [RFC] Use GitLab Milestones, Jean Abou Samra, 2020/06/23
- Re: [RFC] Use GitLab Milestones, Jonas Hahnfeld, 2020/06/23
- Re: [RFC] Use GitLab Milestones, Carl Sorensen, 2020/06/23
- Re: [RFC] Use GitLab Milestones,
Jonas Hahnfeld <=
- Re: [RFC] Use GitLab Milestones, Carl Sorensen, 2020/06/23
- Re: [RFC] Use GitLab Milestones, Valentin Villenave, 2020/06/23
- Re: [RFC] Use GitLab Milestones, Jonas Hahnfeld, 2020/06/24
Re: [RFC] Use GitLab Milestones, James, 2020/06/24
Re: [RFC] Use GitLab Milestones, David Kastrup, 2020/06/24
Re: [RFC] Use GitLab Milestones, Jean Abou Samra, 2020/06/24
Re: [RFC] Use GitLab Milestones, Jonas Hahnfeld, 2020/06/24
Re: [RFC] Use GitLab Milestones, Jonas Hahnfeld, 2020/06/24
Re: [RFC] Use GitLab Milestones, Jonas Hahnfeld, 2020/06/26
Re: [RFC] Use GitLab Milestones, Jonas Hahnfeld, 2020/06/29