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
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 re
+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 wrote:
> I would also like to get at least the Profile Manager in 3.0, which would
> a
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 bran
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
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 Window
