[prev in list] [next in list] [prev in thread] [next in thread]
List: wireshark-dev
Subject: Re: [Wireshark-dev] How to close migrated issues without a merge?
From: chuck c <bubbasnmp () gmail ! com>
Date: 2020-10-27 1:07:13
Message-ID: CAF4O9rT3zX0U5O-et8QjxhCuZLmUXygGUhy-vHskzcObHcgBdw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I finally got around to checking how many I had open and was shocked to see
2% of all open issues were me.
So I'm in fix it or close it mode.
Just occurred to me recently that I can have my own messy issues list on my
Wireshark mirror. :-)
On Mon, Oct 26, 2020 at 7:53 PM John Thacker <johnthacker@gmail.com> wrote:
> My understanding is that people have to be made members at the "Reporter"
> level or higher in order to close issues (which is moving issues to the
> Closed list) or otherwise manage them (label, etc.)
>
> https://docs.gitlab.com/ee/user/project/issue_board.html#permissions
>
> https://docs.gitlab.com/ee/user/permissions.html#project-members-permissions
>
> Since the project doesn't have people with Reporter level membership, it's
> really just the core team members that can close issues.
> (Effectively, merging gates them the same way since the core team must
> approve merges.)
>
> Here's another obvious example that should be closed, regarding Bugzilla
> and MIME types of files:
> https://gitlab.com/wireshark/wireshark/-/issues/8476
>
> John
>
> On Mon, Oct 26, 2020, 8:26 PM chuck c <bubbasnmp@gmail.com> wrote:
>
>> Example closed with a merge:
>> https://gitlab.com/wireshark/wireshark/-/issues/16000
>> Opened 1 year ago by Wireshark GitLab MigrationGuest
>> AndersBroman @AndersBroman closed via merge request !718 (merged) 15
>> hours ago
>>
>> No code to merge. Doing housekeeping.
>> https://gitlab.com/wireshark/wireshark/-/issues/16347
>> Opened 9 months ago by Wireshark GitLab MigrationGuest
>>
>> Added a comment showing the fix but can't close the issue.
>> Is there a way to assign issues back to the person that opened it on
>> bugziila?
>>
>> ___________________________________________________________________________
>> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
>> Archives: https://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>> mailto:wireshark-dev-request@wireshark.org
>> ?subject=unsubscribe
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@wireshark.org
> ?subject=unsubscribe
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_default" style="font-size:small">I finally got \
around to checking how many I had open and was shocked to see 2% of all open issues \
were me.</div><div class="gmail_default" style="font-size:small">So I'm in fix it \
or close it mode. </div><div class="gmail_default" style="font-size:small">Just \
occurred to me recently that I can have my own messy issues list on my Wireshark \
mirror. :-)</div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Mon, Oct 26, 2020 at 7:53 PM John Thacker <<a \
href="mailto:johnthacker@gmail.com">johnthacker@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
dir="auto"><div dir="auto">My understanding is that people have to be made members at \
the "Reporter" level or higher in order to close issues (which is moving \
issues to the Closed list)<span class="gmail_default" \
style="font-family:arial,sans-serif"> or otherwise manage them (label, \
etc.)</span></div><div dir="auto"><br></div><a \
href="https://docs.gitlab.com/ee/user/project/issue_board.html#permissions" \
target="_blank">https://docs.gitlab.com/ee/user/project/issue_board.html#permissions</a></div><div \
dir="auto"><div class="gmail_default" style="font-family:arial,sans-serif"><a \
href="https://docs.gitlab.com/ee/user/permissions.html#project-members-permissions" \
target="_blank">https://docs.gitlab.com/ee/user/permissions.html#project-members-permissions</a></div><div \
class="gmail_default" style="font-family:arial,sans-serif"><br></div><div \
class="gmail_default" style="font-family:arial,sans-serif">Since the project \
doesn't have people with Reporter level membership, it's really just the core \
team members that can close issues.</div></div><div dir="auto"><div \
class="gmail_default" style="font-family:arial,sans-serif">(Effectively, merging \
gates them the same way since the core team must approve merges.)</div></div><div \
dir="auto"><br></div><div dir="auto"><div class="gmail_default" \
style="font-family:arial,sans-serif">Here's another obvious example that should \
be closed, regarding Bugzilla and MIME types of files:</div><div \
class="gmail_default" style="font-family:arial,sans-serif"><a \
href="https://gitlab.com/wireshark/wireshark/-/issues/8476" \
target="_blank">https://gitlab.com/wireshark/wireshark/-/issues/8476</a> </div><div \
class="gmail_default" style="font-family:arial,sans-serif"><br></div><div \
class="gmail_default" \
style="font-family:arial,sans-serif">John</div></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 26, 2020, 8:26 PM \
chuck c <<a href="mailto:bubbasnmp@gmail.com" \
target="_blank">bubbasnmp@gmail.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" \
style="font-size:small">Example closed with a merge:</div><div class="gmail_default" \
style="font-size:small"><a \
href="https://gitlab.com/wireshark/wireshark/-/issues/16000" rel="noreferrer" \
target="_blank">https://gitlab.com/wireshark/wireshark/-/issues/16000</a><br></div><div \
class="gmail_default" style="font-size:small"> Opened 1 year ago by Wireshark GitLab \
MigrationGuest<br></div><div class="gmail_default" \
style="font-size:small">AndersBroman @AndersBroman closed via merge request !718 \
(merged) 15 hours ago<br></div><div class="gmail_default" \
style="font-size:small"><br></div><div class="gmail_default" \
style="font-size:small">No code to merge. Doing housekeeping.</div><div \
class="gmail_default" style="font-size:small"><a \
href="https://gitlab.com/wireshark/wireshark/-/issues/16347" rel="noreferrer" \
target="_blank">https://gitlab.com/wireshark/wireshark/-/issues/16347</a><br></div><div \
class="gmail_default" style="font-size:small">Opened 9 months ago by Wireshark GitLab \
MigrationGuest<br></div><div class="gmail_default" \
style="font-size:small"><br></div><div class="gmail_default" \
style="font-size:small">Added a comment showing the fix but can't close the \
issue.</div><div class="gmail_default" style="font-size:small">Is there a way to \
assign issues back to the person that opened it on bugziila?</div></div> \
___________________________________________________________________________<br> Sent \
via: Wireshark-dev mailing list <<a href="mailto:wireshark-dev@wireshark.org" \
rel="noreferrer" \
target="_blank">wireshark-dev@wireshark.org</a>><br>
Archives: <a href="https://www.wireshark.org/lists/wireshark-dev" \
rel="noreferrer noreferrer" \
target="_blank">https://www.wireshark.org/lists/wireshark-dev</a><br>
Unsubscribe: <a href="https://www.wireshark.org/mailman/options/wireshark-dev" \
rel="noreferrer noreferrer" \
target="_blank">https://www.wireshark.org/mailman/options/wireshark-dev</a><br> \
mailto:<a href="mailto:wireshark-dev-request@wireshark.org" rel="noreferrer" \
target="_blank">wireshark-dev-request@wireshark.org</a>?subject=unsubscribe</blockquote></div>
___________________________________________________________________________<br>
Sent via: Wireshark-dev mailing list <<a \
href="mailto:wireshark-dev@wireshark.org" \
target="_blank">wireshark-dev@wireshark.org</a>><br>
Archives: <a href="https://www.wireshark.org/lists/wireshark-dev" \
rel="noreferrer" target="_blank">https://www.wireshark.org/lists/wireshark-dev</a><br>
Unsubscribe: <a href="https://www.wireshark.org/mailman/options/wireshark-dev" \
rel="noreferrer" target="_blank">https://www.wireshark.org/mailman/options/wireshark-dev</a><br>
mailto:<a href="mailto:wireshark-dev-request@wireshark.org" \
target="_blank">wireshark-dev-request@wireshark.org</a>?subject=unsubscribe</blockquote></div>
[Attachment #6 (text/plain)]
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic