Verifying issues on Gitlab

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

Verifying issues on Gitlab

Federico Bruni-2
Hi all

I've started verifying issues on Gitlab.
It's quite straightforward, but still boring :-)
I think that most of the times it's "useless", meaning that I can't
find any error.. but sometimes you may find something useful to report:
a new command to be documented, an unclear new feature, etc.

The problem is that the number of issues to be verified, only for
2.21.0, is still huge (552):
https://gitlab.com/lilypond/lilypond/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=Fixed_2_21_0&label_name[]=Status%3A%3AFixed

and only 21 issues have been verified so far:
https://gitlab.com/lilypond/lilypond/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=Fixed_2_21_0&label_name[]=Status%3A%3AVerified

If nobody else jumps in, I will probably give up soon.




Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

David Kastrup
Federico Bruni <[hidden email]> writes:

> Hi all
>
> I've started verifying issues on Gitlab.
> It's quite straightforward, but still boring :-)
> I think that most of the times it's "useless", meaning that I can't
> find any error.. but sometimes you may find something useful to
> report: a new command to be documented, an unclear new feature, etc.
>
> The problem is that the number of issues to be verified, only for
> 2.21.0, is still huge (552):
> https://gitlab.com/lilypond/lilypond/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=Fixed_2_21_0&label_name[]=Status%3A%3AFixed
>
> and only 21 issues have been verified so far:
> https://gitlab.com/lilypond/lilypond/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=Fixed_2_21_0&label_name[]=Status%3A%3AVerified
>
> If nobody else jumps in, I will probably give up soon.

The verification was more about checking that a particular commit made
it into a particular version if I remember correctly.  "A new command to
be documented, an unclear new feature, etc..." is above the pay grade of
the Bug Squad basically asked to do the verification (I know, I know:
I've not exactly been great at keeping our infrastructure workers
recruited and dedicated).

--
David Kastrup

Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Karlin High
In reply to this post by Federico Bruni-2
On 5/11/2020 5:01 PM, Federico Bruni wrote:
> If nobody else jumps in, I will probably give up soon.

If someone wants to help, are there step-by-step directions anywhere?
--
Karlin High
Missouri, USA

Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Federico Bruni-2


Il giorno lun 11 mag 2020 alle 17:12, Karlin High
<[hidden email]> ha scritto:
> On 5/11/2020 5:01 PM, Federico Bruni wrote:
>> If nobody else jumps in, I will probably give up soon.
>
> If someone wants to help, are there step-by-step directions anywhere?
>

Start from this list:
https://gitlab.com/lilypond/lilypond/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=Fixed_2_21_0&label_name[]=Status%3A%3AFixed

In the last comment you should find a commit id (if it's missing you'll
have to search it).
The easiest and quickest way to verify that a certain id has been
included in the release tag label used in the issue is using Github.
Start from this URL:

https://github.com/lilypond/lilypond/commit/

then append the commit id you want to verify, e.g.:

https://github.com/lilypond/lilypond/commit/bed9afff763d274af3a2608bdbbc61c807653dbd

At the beginning you'll see the branches and the tags where this commit
is present.
The oldest release tag is the one which should be used as label in the
Gitlab issue.

If everything seems Ok to you, just change the status to Verified.
Click on Edit in the Labels section and as you start typing status,
Gitlab will list the possible entries and you can select Verified,
which will replace Accepted.

More details (out-of-date) here:
http://lilypond.org/doc/v2.21/Documentation/contributor/the-bug-squad




Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Trevor Daniels
In reply to this post by Federico Bruni-2
Federico, you wrote 11/05/2020 23:01:14

>
>I've started verifying issues on Gitlab.
>It's quite straightforward, but still boring :-)
>I think that most of the times it's "useless", meaning that I can't find any error.. but sometimes you may find something useful to report: a new command to be documented, an unclear new feature, etc.
>
>The problem is that the number of issues to be verified, only for 2.21.0, is still huge (552):
>https://gitlab.com/lilypond/lilypond/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=Fixed_2_21_0&label_name[]=Status%3A%3AFixed
>
>and only 21 issues have been verified so far:
>https://gitlab.com/lilypond/lilypond/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=Fixed_2_21_0&label_name[]=Status%3A%3AVerified
>
>If nobody else jumps in, I will probably give up soon.
I've verified a few this evening, and will keep plugging away slowly
from time to time ... at least for a while.

Trevor



Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Carl Sorensen-3
In reply to this post by Federico Bruni-2
Federico,

Thanks for the clear instructions.  I'll start jumping in, but it will probably be on the order of about 10 per day, give or take.

I think we can get this under control eventually....

Thanks,

Carl


Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Caio Barros
In reply to this post by Federico Bruni-2
Em seg., 11 de mai. de 2020 às 19:29, Federico Bruni <[hidden email]>
escreveu:

> Start from this list:
>
> https://gitlab.com/lilypond/lilypond/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=Fixed_2_21_0&label_name[]=Status%3A%3AFixed
>
> In the last comment you should find a commit id (if it's missing you'll
> have to search it).
> The easiest and quickest way to verify that a certain id has been
> included in the release tag label used in the issue is using Github.
> Start from this URL:
>
> https://github.com/lilypond/lilypond/commit/
>
> then append the commit id you want to verify, e.g.:
>
>
> https://github.com/lilypond/lilypond/commit/bed9afff763d274af3a2608bdbbc61c807653dbd
>
> At the beginning you'll see the branches and the tags where this commit
> is present.
> The oldest release tag is the one which should be used as label in the
> Gitlab issue.
>
> If everything seems Ok to you, just change the status to Verified.
> Click on Edit in the Labels section and as you start typing status,
> Gitlab will list the possible entries and you can select Verified,
> which will replace Accepted.
>
> More details (out-of-date) here:
> http://lilypond.org/doc/v2.21/Documentation/contributor/the-bug-squad


If it's ok with you I can help as well but I think I don't have permission
to edit the labels.

Anyway, thanks for the steps.

Caio
Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Carl Sorensen-3
In reply to this post by Federico Bruni-2
Hey, we're down to 520!

BTW, instead of scrolling to the bottom of the comments to find the commit id, it's easier to set the sorting of the comments to "newest first", which puts the commit ID very near the top.

Maybe I can get us under 500 before I go to bed tonight.

Carl


On 5/11/20, 4:29 PM, "lilypond-devel on behalf of Federico Bruni" <lilypond-devel-bounces+c_sorensen=[hidden email] on behalf of [hidden email]> wrote:



Il giorno lun 11 mag 2020 alle 17:12, Karlin High
<[hidden email]> ha scritto:
> On 5/11/2020 5:01 PM, Federico Bruni wrote:
>> If nobody else jumps in, I will probably give up soon.
>
> If someone wants to help, are there step-by-step directions anywhere?
>

Start from this list:
https://gitlab.com/lilypond/lilypond/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=Fixed_2_21_0&label_name[]=Status%3A%3AFixed

In the last comment you should find a commit id (if it's missing you'll
have to search it).
The easiest and quickest way to verify that a certain id has been
included in the release tag label used in the issue is using Github.
Start from this URL:

https://github.com/lilypond/lilypond/commit/

then append the commit id you want to verify, e.g.:

https://github.com/lilypond/lilypond/commit/bed9afff763d274af3a2608bdbbc61c807653dbd

At the beginning you'll see the branches and the tags where this commit
is present.
The oldest release tag is the one which should be used as label in the
Gitlab issue.

If everything seems Ok to you, just change the status to Verified.
Click on Edit in the Labels section and as you start typing status,
Gitlab will list the possible entries and you can select Verified,
which will replace Accepted.

More details (out-of-date) here:
http://lilypond.org/doc/v2.21/Documentation/contributor/the-bug-squad





Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Kevin Barry
In reply to this post by Federico Bruni-2
Hi Federico,

Thank you for the instructions. I will try to help get them done as
well.

On Tue, May 12, 2020 at 12:28:24AM +0200, Federico Bruni wrote:
> In the last comment you should find a commit id (if it's missing you'll have
> to search it).
> The easiest and quickest way to verify that a certain id has been included
> in the release tag label used in the issue is using Github. Start from this
> URL:

Another handy way to do this is to run git tag --contains <commit_hash>.
(For me this is faster than github.)

Kevin

Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Federico Bruni-2
Il giorno mar 12 mag 2020 alle 08:15, Kevin Barry <[hidden email]>
ha scritto:
> Another handy way to do this is to run git tag --contains
> <commit_hash>.
> (For me this is faster than github.)

Right, I forgot it.
It's faster indeed.

Thanks to everybody for jumping in so quickly!




Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Davide Liessi-2
In reply to this post by Carl Sorensen-3
Dear Federico,

I can contribute too, probably on the same order as Carl:

Il giorno mar 12 mag 2020 alle ore 01:12 Carl Sorensen
<[hidden email]> ha scritto:
> I'll start jumping in, but it will probably be on the order of about 10 per day, give or take.

Can you give me the appropriate permissions?
My GitLab name is dliessi.

Best wishes.
Davide

Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Jonas Hahnfeld
Am Dienstag, den 12.05.2020, 10:03 +0200 schrieb Davide Liessi:

> Dear Federico,
>
> I can contribute too, probably on the same order as Carl:
>
> Il giorno mar 12 mag 2020 alle ore 01:12 Carl Sorensen
> <[hidden email]> ha scritto:
> > I'll start jumping in, but it will probably be on the order of about 10 per day, give or take.
>
> Can you give me the appropriate permissions?
> My GitLab name is dliessi.
Granted 'Reporter' access for now, let me know if you need 'Developer'
to also push branches (note that you can always fork & open a merge
request from there; it's not strictly necessary anymore to be a member
somewhere before contributing).

Jonas

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re[2]: Verifying issues on Gitlab

Trevor Daniels
In reply to this post by Kevin Barry
Another question:

How do I remove labels no longer relevant (or entered incorrectly!) eg
Patch:Push for verified issues?

Trevor

------ Original Message ------
From: "Kevin Barry" <[hidden email]>
To: "Federico Bruni" <[hidden email]>
Cc: "lilypond-devel" <[hidden email]>
Sent: 12/05/2020 08:15:02
Subject: Re: Verifying issues on Gitlab

>Hi Federico,
>
>Thank you for the instructions. I will try to help get them done as
>well.
>
>On Tue, May 12, 2020 at 12:28:24AM +0200, Federico Bruni wrote:
>>  In the last comment you should find a commit id (if it's missing you'll have
>>  to search it).
>>  The easiest and quickest way to verify that a certain id has been included
>>  in the release tag label used in the issue is using Github. Start from this
>>  URL:
>
>Another handy way to do this is to run git tag --contains <commit_hash>.
>(For me this is faster than github.)
>
>Kevin
>


Reply | Threaded
Open this post in threaded view
|

Re: Re[2]: Verifying issues on Gitlab

Jonas Hahnfeld
Am Dienstag, den 12.05.2020, 11:19 +0000 schrieb Trevor:
> Another question:
>
> How do I remove labels no longer relevant (or entered incorrectly!) eg
> Patch:Push for verified issues?

If using the UI, click "Edit" next to the labels, find the one you want
to remove and untick. For the lazy, type '/unlabel ~' and pick the
right one from the dropdown that appears when JS is enabled 😉

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Verifying issues on Gitlab

Carl Sorensen-3
In reply to this post by Federico Bruni-2


On 5/12/20, 1:33 AM, "lilypond-devel on behalf of Federico Bruni" <lilypond-devel-bounces+c_sorensen=[hidden email] on behalf of [hidden email]> wrote:

Thanks to everybody for jumping in so quickly!

-> CS  We're now down to 150 issues to be verified.  This is great news!

Carl