<<On Sat, 9 Dec 2017 08:05:51 +0100, Franco Fichtner <franco at
lastsummer.de> said:
> Hi,
>> On 8. Dec 2017, at 8:25 PM, FreeBSD Security Officer
<security-officer at freebsd.org> wrote:
>>
>>
+--------------------------------------------------+-----------------------+
>> |releng/11.1|11.1-RELEASE|n/a |July 26, 2017 |11.2-RELEASE + 3
months|
>>
+--------------------------------------------------+-----------------------+
> Is there *any* indication when X + 3 is going to be? Because as a
downstream
> vendor X + 3 months usually translates to X, because there is no time to
prepare
> for any of this, especially when swift adoption is enforced by upstream,
e.g.
> by deprecated packages, quarterly branch and locking users out of the ports
tree.
Yeah, that's been one of my concerns all along with this new
deprecation schedule. It takes me about a month to qualify a new
release, and we have only two windows a year when I can actually
deploy it (after testing) -- from 12/26 to 12/30, and from the Monday
after the first Saturday in June until the Friday before the first
Monday in September.[1] Release schedules in recent years have been
pretty pessimal for me as it is. I'll be rolling out 11.1 later this
month, but if 11.2 were to happen in March I'd be SOL before I could
even think about upgrading.
-GAWollman
[1] And not coincidentally, these are the times when everybody, myself
included, wants to go on vacation.