Re: [Wireshark-dev] 2.5.0, 2.6, and 3.0 release planning

Actually, I'd also much rather prefer to create one 2.6 and create 2.5 as a -rc. It would make developing that much easier. If we plan on release 2.5 as a regular release that I am fine with it. cheers Roland On Sun, Feb 4, 2018 at 9:13 PM, Alexis La Goutte wrote: >

Re: [Wireshark-dev] 2.5.0, 2.6, and 3.0 release planning

On Fri, Feb 2, 2018 at 11:45 PM, Gerald Combs wrote: > I think we've fixed the major issues identified by Stig, Jim, and others > so I'd like to release 2.5.0 on February 6. This would let us release 2.6.0 > this spring, followed by 3.0.0 in the fall: > > > March: Create

Re: [Wireshark-dev] 2.5.0, 2.6, and 3.0 release planning

yes, those should be fixed before a 2.6 release. For 2.5 I think it could be ok. cheers Roland On Sat, Feb 3, 2018 at 12:52 PM, Jakub Zawadzki wrote: > Hello, > > W dniu 2018-02-02 23:45, Gerald Combs napisał(a): > >> I think we've fixed the major issues identified

Re: [Wireshark-dev] 2.5.0, 2.6, and 3.0 release planning

Hello, W dniu 2018-02-02 23:45, Gerald Combs napisał(a): I think we've fixed the major issues identified by Stig, Jim, and others so I'd like to release 2.5.0 on February 6. In oss-fuzz queue currently there are few crashes, and one inifite loop. Should it be a blocker for a release?

Re: [Wireshark-dev] 2.5.0, 2.6, and 3.0 release planning

On Fri, Feb 2, 2018 at 11:45 PM, Gerald Combs wrote: > I think we've fixed the major issues identified by Stig, Jim, and others so > I'd like to release 2.5.0 on February 6. Maybe not a show stopper the release, but selecting a byte in the ByteView does not expand the

[Wireshark-dev] 2.5.0, 2.6, and 3.0 release planning

I think we've fixed the major issues identified by Stig, Jim, and others so I'd like to release 2.5.0 on February 6. This would let us release 2.6.0 this spring, followed by 3.0.0 in the fall: March: Create master-2.6 after one or two 2.5.x releases. April: Release 2.6.0, probably after