On 4/11/19 4:54 PM, Gerald Combs wrote:
> We currently have three active release branches: 3.0, 2.6, and 2.4. This is
> because we support each release branch for a set amount of time (typically 24
> months after the initial .0 release) and our last three .0 releases were less
> than 12 months
crement
> the MINOR for development branch.
>
> Cheers,
> Ross
>
> On Fri, Apr 12, 2019 at 8:30 AM Anders Broman
> wrote:
>
>>
>>
>>
>>
>> *From:* Wireshark-dev *On Behalf
>> Of *graham.shanks via Wireshark-dev
>> *Sent:* den 12 apri
+1 for having only two supported stable versions.
One as a „long term support“ branch (e.g. 2.6 at the moment)
and one „normal“ stable (eg. 3.0 atm or next 3.2)
+1 for keeping odd minor numbers for development versions.
Maybe having a monthly rolling release with latests features to have more
ia
> Wireshark-dev
> Sent: den 12 april 2019 09:04
> To: Developer support list for Wireshark <mailto:wireshark-dev@wireshark.org>>
> Cc: graham.shanks <mailto:graham.sha...@blueyonder.co.uk>>
> Subject: Re: [Wireshark-dev] Release lifetime and version number changes?
On Thu, Apr 11, 2019 at 6:55 PM Gerald Combs wrote:
> We currently have three active release branches: 3.0, 2.6, and 2.4. This
> is because we support each release branch for a set amount of time
> (typically 24 months after the initial .0 release) and our last three .0
> releases were less than
minor correction, it should not read "sullify" but pacify. It has been a
long week
Am Fr., 12. Apr. 2019 um 15:01 Uhr schrieb Roland Knall :
> Just my two cents, I like a clear indication, that I am working with a
> development version beyond the obvious changes of text. SO the versioning
>
Just my two cents, I like a clear indication, that I am working with a
development version beyond the obvious changes of text. SO the versioning
is usually the first thing I look at.
That being said, I could imagine adopting the Python versioning scheme as
an alternative to the current even/odd
On Thu, Apr 11, 2019 at 7:55 PM Gerald Combs wrote:
> We currently have three active release branches: 3.0, 2.6, and 2.4. This
> is because we support each release branch for a set amount of time
> (typically 24 months after the initial .0 release) and our last three .0
> releases were less than
On Fri, 12 Apr 2019 at 00:55, Gerald Combs wrote:
> We currently have three active release branches: 3.0, 2.6, and 2.4. This
> is because we support each release branch for a set amount of time
> (typically 24 months after the initial .0 release) and our last three .0
> releases were less than
roman
wrote:
>
>
>
>
> *From:* Wireshark-dev *On Behalf Of
> *graham.shanks via Wireshark-dev
> *Sent:* den 12 april 2019 09:04
> *To:* Developer support list for Wireshark
> *Cc:* graham.shanks
> *Subject:* Re: [Wireshark-dev] Release lifetime and version n
From: Wireshark-dev On Behalf Of
graham.shanks via Wireshark-dev
Sent: den 12 april 2019 09:04
To: Developer support list for Wireshark
Cc: graham.shanks
Subject: Re: [Wireshark-dev] Release lifetime and version number changes?
>I think dropping the even/odd scheme is a good i
I think dropping the even/odd scheme is a good idea.Personally I'd go down to
2 active branches but then my group wouldn't be adversely affected by dropping
the "old old stable" version since we invariably use the stable version. More
weight should be given to the opinions of people who do
12 matches
Mail list logo
