Re: Rethinking the Postfix release schedule

2019-01-31 Thread Wietse Venema
Andrey Repin: [ Charset windows-1250 converted... ] > Greetings, Wietse Venema! > > > I do not care much what other projects do. > > Did I say you do? I just outlined two most common approaches, with examples. Well, I don't like bringing up PHP in a discussion about Postfix :-( > > Postfix has

Re: Rethinking the Postfix release schedule

2019-01-31 Thread Andrey Repin
Greetings, Wietse Venema! > I do not care much what other projects do. Did I say you do? I just outlined two most common approaches, with examples. > Postfix has a good record for quality, stability and compatibility, and it > supports four stable releases, each release receiving updates for fou

Re: Rethinking the Postfix release schedule

2019-01-31 Thread Matus UHLAR - fantomas
On January 31, 2019 11:10:50 AM UTC, Matus UHLAR - fantomas wrote: while debian and ubuntu LTS have 2-year cycle and 5-year LTS support, yes, that can get near 8 years behind. On 31.01.19 11:22, Jim Popovitch wrote: Debian has no strict release cycles, and Debian's LTS is based on several fa

Re: Rethinking the Postfix release schedule

2019-01-31 Thread Postfix User
On Wed, 30 Jan 2019 21:14:07 -0500, Richard Damon stated: FreeBSD users already have a choice of either the latest postfix version, Postfix 3.3 stable release or the latest beta version,Postfix 3.4 experimental release. I don't know if there is a good reason to modify the release dates, at least

Re: Rethinking the Postfix release schedule

2019-01-31 Thread Jim Popovitch
On January 31, 2019 11:10:50 AM UTC, Matus UHLAR - fantomas wrote: >while debian and ubuntu LTS have 2-year cycle and 5-year LTS support, yes, >that can get near 8 years behind. Debian has no strict release cycles, and Debian's LTS is based on several factors including $$, time, and personnel.

Re: Rethinking the Postfix release schedule

2019-01-31 Thread Matus UHLAR - fantomas
On 30.01.19 16:38, Wietse Venema wrote: One problem with LTS releases is that down-stream distros can end up running very old code (for example with 4-year LTS up-stream, a down-stream distro with 4-year LTS can end up running 8-year old code, which is really a pain to support on a mailing list l