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>> 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>>: > > 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 > > ___________________________________________________________________________ > 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
