Qt 5.12 would bump our minimum macOS requirement to 10.12. According to our web server logs, about 5% of our macOS visitors are still running 10.11 and 10.10. Which would generate more complaints: not supporting dark mode or not supporting older macOS releases?
On 12/13/18 4:21 AM, Roland Knall wrote: > I would opt for switching the mac builders for 3.0 to 5.12 as well, as it > would help with the integration of the Dark Mode or better, it would allow > for the proper integration of Dark Mode. > > cheers > > Am Do., 13. Dez. 2018 um 00:12 Uhr schrieb Gerald Combs > <ger...@wireshark.org <mailto:ger...@wireshark.org>>: > > I switched the master Windows builders to Qt 5.12.0 ahead of the 2.9.0 > release. If there are any major issues it's easy enough switch back to > 5.9.7. > > On 12/12/18 10:51 AM, Maynard, Chris wrote: > > In preparation for 2.9.0 and 3.0, I'm not sure if there's also any > interest in migrating the Windows buildbots to the latest Qt LTS > release, 5.12.0, which was just released on December 6, 2018? I've > successfully compiled Wireshark master with it with no issues, except > for the missing PDB (which was also showing up with 5.11.2), and which > generates this single warning: > > > > qtmain.lib(qtmain_win.obj) : warning LNK4099: PDB > 'qtmain.pdb' was not > > found with 'qtmain.lib(qtmain_win.obj)' or at '<build output > directory> > > \run\RelWithDebInfo\qtmain.pdb'; linking object as > if no debug info > > > > Current build information, for reference: > > Version 2.9.0 (v2.9.0rc0-2804-g9711abc9) > > > > Compiled (64-bit) with Qt 5.12.0, with WinPcap SDK (WpdPack) 4.1.2, > with GLib 2.52.2, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.14.0, > with Lua 5.2.4, with GnuTLS 3.4.11, with Gcrypt 1.8.3, with MIT > Kerberos, with MaxMind DB resolver, with nghttp2 1.14.0, with LZ4, with > Snappy, with libxml2 2.9.4, with QtMultimedia, with AirPcap, with SBC, > with SpanDSP, with bcg729. > > > > Running on 64-bit Windows 10 (1809), build 17763, with Intel(R) > Xeon(R) CPU E3-1505M v5 @ 2.80GHz (with SSE4.2), with 16225 MB of > physical memory, with locale English_United States.1252, with WinPcap > version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version > 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.4.11, with Gcrypt 1.8.3, > with AirPcap 4.1.0 build 1622, binary plugins supported (14 loaded). > Built using Microsoft Visual Studio 2017 (VC++ 14.15, build 26730). > > > > - Chris > > Ref: http://blog.qt.io/blog/2018/12/06/qt-5-12-lts-released/ > > > > -----Original Message----- > > From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org > <mailto:wireshark-dev-boun...@wireshark.org>] On Behalf Of Gerald Combs > > Sent: Wednesday, December 12, 2018 12:40 PM > > To: Developer support list for Wireshark <wireshark-dev@wireshark.org > <mailto:wireshark-dev@wireshark.org>> > > Subject: Re: [Wireshark-dev] 2.9.0 and 3.0.0 release schedule > > > > [THIS MESSAGE ORIGINATED FROM A NON-IGT EMAIL ADDRESS] > > > > > > > > Delaying the 3.0 release is fine with me. I've updated my calendar as > follows: > > > > December 12 (today): Release 2.9.0 > > January 9: Branch master-3.0 > > January 30: Release 3.0.0 > > > > On 12/12/18 7:04 AM, Alexis La Goutte wrote: > >> +1 for delayed the 3.0 release > >> > >> Always kept a 2.9 for this week and only branch after some feature > >> (like Profile Manager...) merged (For middle of Junary ?) > >> > >> Cheers > >> > >> On Wed, Dec 12, 2018 at 2:50 PM Roland Knall <rkn...@gmail.com > <mailto:rkn...@gmail.com> > >> <mailto:rkn...@gmail.com <mailto:rkn...@gmail.com>>> wrote: > >> > >> I would also like to get at least the Profile Manager in 3.0, which > >> would allow for downloading/uploading the profiles as .zip file, > making > >> handling a lot easier. > >> > >> Could we rather target a time-window around end of jannuary / > beginning > >> of february? Would still be enough time to get the candidate ready > >> for SFUS > >> > >> regards > >> > >> Am Mi., 12. Dez. 2018 um 13:56 Uhr schrieb Peter Wu > >> <pe...@lekensteyn.nl <mailto:pe...@lekensteyn.nl> > <mailto:pe...@lekensteyn.nl <mailto:pe...@lekensteyn.nl>>>: > >> > >> Hi Gerald, > >> > >> On Tue, Dec 11, 2018 at 04:51:22PM -0800, Gerald Combs wrote: > >> > I plan on releasing Wireshark 2.9.0 tomorrow, December 12. > If all > >> goes well I'm hoping to create the master-3.0 branch on > December 17 > >> followed by the 3.0.0 release on the 19th. Given the > proximity of > >> the Christmas and New Year holidays I plan on waiting to enable > >> automatic updates to 3.0.0 until the first or second week of > January. > >> > >> I would like to complete the following features/tasks for > the 3.0 > >> release: > >> > >> - RSA decryption support for PKCS #11 tokens. (Only the > >> configuration GUI and User's Guide are unfinished.) > >> - Upgrade GnuTLS on Windows to at least 3.6.0, possibly > include > >> the p11-kit.lib files as well. > >> - Update the User's Guide for decryption block support: > >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15252 > >> > >> One week is a bit tight I think to get all of this done. > Would it be > >> possible to push this after the holidays instead (next year)? > >> -- > >> Kind regards, > >> Peter Wu > >> https://lekensteyn.nl > >> > > ___________________________________________________________________________ > > > > > > > > > > > > > > > > > > > > > > > > CONFIDENTIALITY NOTICE: This message is the property of International > Game Technology PLC and/or its subsidiaries and may contain > proprietary, confidential or trade secret information. This message is > intended solely for the use of the addressee. If you are not the > intended recipient and have received this message in error, please > delete this message from your system. Any unauthorized reading, > distribution, copying, or other use of this message or its attachments > is strictly prohibited. > > > > ___________________________________________________________________________ > > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org > <mailto: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 > <mailto:wireshark-dev-requ...@wireshark.org>?subject=unsubscribe > > > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org > <mailto: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 > <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 > ___________________________________________________________________________ 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