ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Status label for issues

From: Uli Heilmeier <zeugs@xxxxxxxxxxxx>
Date: Tue, 27 Apr 2021 08:43:54 +0200
Diff between current and proposal list:

- incident
- question
- cli::tshark
+ ui::tshark
- ui::gtk
- version::0.x
- version::1.0
- version::1.10
- version::1.12
- version::1.2
- version::1.4
- version::1.6
- version::1.8
- version::2.0
- version::2.2
- version::2.4
- version::2.6
- version::3.0
+ version::outdated
+ ws-status::unconfirmed
+ ws-status::confirmed
+ ws-status::waiting-for-response
+ ws-status::in-progress
+ ws-status::invalid
+ ws-status::wontfix
+ ws-status::fixed
+ ws-status::duplicate

I have no strong feelings about the os::* labels. We can reduce them to os::mac, os::windows, os::linux, os::unix.


Am 26.04.21 um 23:13 schrieb Roland Knall:
> The list seems to be duplicated with the lists from above. Anyhow, it seems we just have too many labels already, and I
> am still not convinced that they can be used properly and consistently at this point
> 
> I would clean up the proposal list first, then from there figure out which items we need on the list
> 
> cheers
> Roladn