Wireshark-dev: [Wireshark-dev] question regarding merge request workflow
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Robert Frohl <rfrohl@xxxxxxxx>
Date: Wed, 11 Nov 2020 14:47:40 +0100
Hi wireshark devs,

in my role as wireshark maintainer for openSUSE/SUSE I go a request for
SMCD(v2) protocol support. Which has a pending merge request [0]. With
the recent 3.4.0 release I suspect that the only option to fullfill this
request on short notice is a backport to 3.4.

I was wondering how these merge requests are usually handled process
wise. Is there an indication that the change is looking good and might
be accepted? There is no detailed description of what to look for, that
I could find (found only [1]).

What is the potential timeline of such a review ?

Thanks,
Robert

[0] https://gitlab.com/wireshark/wireshark/-/merge_requests/795
[1]
https://gitlab.com/wireshark/wireshark/-/wikis/Development/SubmittingPatches#the-review-process
-- 
Security Engineer/wireshark maintainer, SUSE Software Solutions Germany
GmbH, Maxfeldstr. 5, 90409 Nürnberg, GF: Felix Imendörffer (HRB 36809,
AG Nürnberg)

Attachment: OpenPGP_0x089EDB3D230A2404.asc
Description: application/pgp-keys

Attachment: OpenPGP_signature
Description: OpenPGP digital signature