Release schedule plans

[Damien Miller]

Harri Vartiainen wrote:
> Gervase Markham wrote:
> 
>> It seems that we have three choices:
>>
>> a) Release 2.18 and release 2.20 soon afterwards
>> b) Release 2.18, unfreeze for a bit, and release 2.20 in (say) June
>> c) Abandon 2.18 and just release 2.20
> 
> 
>  From the users point of view, release  "official stable version" as 
> fast as possible. Don't care if it is 2.18 or 2.20. There's huge gap 
> between "developer versions" and version 2.16.x.

(delurk)

Since we are talking about users, I'll add my opinion :) I run the
OpenSSH bugzilla, currently using 2.16 and I'm waiting for the next
stable release because it has features that would be useful for myself
and the other developers.

I don't care even a little bit what the next stable version is numbered,
but I don't want to have to do the upgrade dance repeatedly in the space
of a month or two to track the latest stable version.

I'll also mention that I don't consider it acceptable to sit for over
one month on a security bugfix, just because it doesn't fit with your
releasing plans. That is putting the cart before the proverbial horse.

-d