I somewhat feel a little bit more sceptical of increasing the numbers of labels. They would require discipline before being enforceable. Also, we would need some form of documentation to allow a lookup what each label is supposed to be and what eventual escalation procedures would be.
I suggest we create a wiki page for that discussion first, and if we can figure that out create the labels. Also, I would limit the number of labels to as few as possible kind regards Roland Am Sa., 24. Apr. 2021 um 13:33 Uhr schrieb Jirka Novak <j.no...@netsystem.cz >: > Hi Uli, > > > For issues (especially bugs) I really miss the status field which was > available with Bugzilla. > > > > Therefore I would like to create these scoped labels [1]: > > ... > > > > Any objections? Comments are very welcome. > > I agree with you. I'm missing this information about created issues too. > I propose one more kind of label/labels. It is more about interaction > with reporter of the issue - "waiting for response". There are many > issues opened for years where last message is request for sample or more > information. I think that if such issue is opened for years with no > reaction, it is useless and should be closed. > > Best regards, > > Jirka > ___________________________________________________________________________ > 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-requ...@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-requ...@wireshark.org?subject=unsubscribe
