I can smell 2.4!
-
Just deploy on Friday.
Yeah, dump the payload and run away for weekend is a well-proven upgrade strategy. Users will figure out most issues themselves over those 3 days. 8) ;D
Made me think of a large project I single-handedly own, yet is a multi-million dollar contract with $20k/day fines if late. In the contract, we need to have the data ready for the customer within 3 days after the event ends. I told the PM, that sounds fine, I can have the data ready within minutes after the event ends, and automated.
After everything is said and done, turns out the PM promised that data would be cleaned up by us, not just given as the customer supplied it, the event ends at 3:30p Friday, and "3 days" literally means "3 days", not 3 working days. So I have to have everything ready by Monday morning.
My manager at the time apologized and gave me a 14% raise. At least I can now clean up their data in a few tens of minutes after all these years. Lots and lots of scripts, but there is still enough investigation and judgement calls to not be able to automate.
-
Two remaining! ;D
-
100% : 291 issues (291 closed — 0 open)
Let's do it today (Friday) so we have time ahead of us to restore and bring everything back up before Monday! :D 8)
-
This bug scheduled for 2.3.4_2 still freaks me out a bit https://redmine.pfsense.org/issues/7599: System->Update unavailable in WebGUI after connection failure during update. At least it has an easy work around via the console.
-
Two remaining! ;D
And 2.4 is now off the roadmap so it must be happening Monday.
Who's going to be the guinea pigs? And how does 2.3.4_2 play into this now with 2.4 releasing?
-
No more snapshots have been made after 2.4.0.r.20170929.0700, something is happening 8)
-
Are you all slacking, spotted this 5 days ago :P
-
Bad news I think? :)
-
Apparently not a good time to release with the shitton of dnsmasq security issues.
https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.html
-
Apparently not a good time to release with the shitton of dnsmasq security issues.
https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.html
That's good news. Keep up the good work guys :)
-
Are you all slacking, spotted this 5 days ago :P
What gathering is that from?! I want to learn about upcoming DPDK!
-
Sorry folks, it's not happening today!
2.4-RELEASE delayed for 10 days. Will be based on FreeBSD 11.1!
-
Sorry folks, it's not happening today!
2.4-RELEASE delayed for 10 days. Will be based on FreeBSD 11.1!
When can we expect the security patch being pushed to 2.4-RC snapshots.
-
Apparently not a good time to release with the shitton of dnsmasq security issues.
https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.html
And:
https://vuxml.freebsd.org/freebsd/d9e82328-a129-11e7-987e-4f174049b30a.html
https://community.openvpn.net/openvpn/wiki/CVE-2017-12166
-
When can we expect the security patch being pushed to 2.4-RC snapshots.
As soon as we get it fixed.
-
Are you all slacking, spotted this 5 days ago :P
What gathering is that from?! I want to learn about upcoming DPDK!
Google dpdk and also follow gonzopancho on twitter.
-
Just deploy on Friday.
Yeah, dump the payload and run away for weekend is a well-proven upgrade strategy. Users will figure out most issues themselves over those 3 days. 8) ;D
One client I used to work with in the past always deployed updates prior to christmas or before he went on holiday for 2 weeks, often caused chaos, but he wouldnt budge on how he worked. :)
-
Sorry folks, it's not happening today!
2.4-RELEASE delayed for 10 days. Will be based on FreeBSD 11.1!
Interesting so its been decided to not use 11.0 at all for any stable release, I agree with that decision.
-
-
Maybe in Asia/South Pacific.
