It's Friday…



  • It's Friday.. wouldn't it be a great day for a 2.3 release? :)



  • 1 ToDo left, 80% done renaming the ISO files.

    They've been down to 1 remaining quite a few times in the past month. Each time someone has to open their big mouth and find something. "The new RC no longer supports IPv4 and tries to use IPX." Pfffft.. what-ev. We need RTM! It's April and got another few inches of snow. Supports to be 60f soon. Crazy times.



  • IPX?!?! LOL, nice to know I'm not the only old-timer around…  :D



  • Only an idiot does a release on a Friday afternoon, or at least someone who doesn't want to enjoy his weekend.



  • @Harvy66:

    1 ToDo left, 80% done renaming the ISO files.

    They've been down to 1 remaining quite a few times in the past month. Each time someone has to open their big mouth and find something. "The new RC no longer supports IPv4 and tries to use IPX." Pfffft.. what-ev. We need RTM! It's April and got another few inches of snow. Supports to be 60f soon. Crazy times.

    The bug list can be a little misleading.

    1. There are still lots of bugs.  They are just pushed to 2.3.1 and later targets.
    2. There are still issues people are having and discussing in the forum that are not in the bug list.


  • We try to avoid releasing on Fridays. Release is actually built and we could push it today. Not going to though, you'll see it on Monday.

    The image passed around in our internal chat earlier in the week.

    @NOYB:

    1. There are still lots of bugs.  They are just pushed to 2.3.1 and later targets.
    2. There are still issues people are having and discussing in the forum that are not in the bug list.

    Both of those are always true, have always been true, and will always be true. Except the "lots of" part, there are some but few and only a handful of those are regressions and they're minor.



  • I think I'll grab the RC tonight and upgrade on Monday. Unless there is a reason to wait. :)



  • @cmb:

    @NOYB:

    1. There are still lots of bugs.  They are just pushed to 2.3.1 and later targets.
    2. There are still issues people are having and discussing in the forum that are not in the bug list.

    Both of those are always true, have always been true, and will always be true. Except the "lots of" part, there are some but few and only a handful of those are regressions and they're minor.

    Regardless of type, severity, and history (always true, always been true, always will be true) there are in my opinion "lots of" them.

    It's Subjective.  Part of the reason it can be misleading.

    One persons … is another persons...
    Beauty is in the eye of the beholder
    And many more clichés would be fitting I'm sure.



  • @NOYB:

    Regardless of type, severity, and history (always true, always been true, always will be true) there are in my opinion "lots of" them.

    It's Subjective.  Part of the reason it can be misleading.

    I guess you can define "lots" however you want, but there are 8 open 2.3-specific issues. 6 of which are minor cosmetic things, 2 of which are unusual, little-used circumstances. Lots is defined as "a large number", most wouldn't consider 8 to be large. Especially when they're of no consequence to almost everyone.



  • @cellobita:

    IPX?!?! LOL, nice to know I'm not the only old-timer around…  :D

    Actually I was a bit young, and only used Kali.Net to emulate IPX so I could play Doom, Starcraft, and Quake over the Internet. I remember getting the experimental Quake exe that supports TCP/IP. Then came QuakeSpy. First modem was an external 14.4k USRobotics. Dates me, but I'm still young  :-)



  • Dude, you missed out on the whole acoustic coupler thing. You really are young.  :)

    @Harvy66:

    First modem was an external 14.4k USRobotics. Dates me, but I'm still young  :-)



  • @cmb:

    @NOYB:

    Regardless of type, severity, and history (always true, always been true, always will be true) there are in my opinion "lots of" them.

    It's Subjective.  Part of the reason it can be misleading.

    I guess you can define "lots" however you want, but there are 8 open 2.3-specific issues. 6 of which are minor cosmetic things, 2 of which are unusual, little-used circumstances. Lots is defined as "a large number", most wouldn't consider 8 to be large. Especially when they're of no consequence to almost everyone.

    Again.  All that is subjective and just like I can define lots to be whatever quantity suites me same goes for you defining the terms you chose to cite.  Forget open 2.3-specific issues.  Try this - open issues that impact 2.3.  Regardless of whether the are specific only to version 2.3.  In my opinion that is a better gauge the current state.  And is far more that 8.

    My original point was that what is reported in the bug database under the various canned reports can be misleading (emphasis on "can be").  It can be necessary to view it in the context of what it filters and what is trying to be ascertained.



  • @dennypage:

    Dude, you missed out on the whole acoustic coupler thing. You really are young.  :)

    @Harvy66:

    First modem was an external 14.4k USRobotics. Dates me, but I'm still young  :-)

    Okay if we just call you "Falcon"?  (War Games)
    So funny to see some of those old techie movies.  Acoustic coupling 300 baud modems, and "cell" phones the size of boom boxes.



  • Not releasing new software on Friday…..lol HA. never thought about the weekend after as being a reason but hey, I enjoy my weekend not thinking about work just as anyone else. In hindsight though, I had always wondered why Bungie waits till Tuesday to do reset and new releases. Perhaps it is so they can enjoy the weekend and have a day to get past Monday morning face. We all get that that look on Monday morning. That look that says, I can't believe my weekend is over already and I am back in this place so fast.



  • I took the plunge. I cutover from OPNsense to pfsense 2.3 RC.

    Thanks guys!

    How do you get those snazzy pie graphs with the various ports etc…? It was shown in the screenshots for 2.3



  • In general, the grass is greener on the other side, but the PFSense devs seem less sensational and I like that.



  • @usual:

    I took the plunge. I cutover from OPNsense to pfsense 2.3 RC.

    Thanks guys!

    How do you get those snazzy pie graphs with the various ports etc…? It was shown in the screenshots for 2.3

    Think you may be referring to - Status - Diagnostics - Firewall - Summary View



  • @NOYB:

    @usual:

    I took the plunge. I cutover from OPNsense to pfsense 2.3 RC.

    Thanks guys!

    How do you get those snazzy pie graphs with the various ports etc…? It was shown in the screenshots for 2.3

    Think you may be referring to - Status - Diagnostics - Firewall - Summary View

    I don't see that in the menus.



  • Try Status/System Logs/Firewall then 3 choices of Normal View, Dynamic View or Summary View.



  • Yeah what webtyro said.

    Don't know where the gibberish I spewed out came from.



  • Thanks. I'd love to see more of these in the future.. A reporting functionality would be awesome as well.



  • @jbhowlesr:

    Not releasing new software on Friday…..lol HA. never thought about the weekend after as being a reason but hey, I enjoy my weekend not thinking about work just as anyone else. In hindsight though, I had always wondered why Bungie waits till Tuesday to do reset and new releases. Perhaps it is so they can enjoy the weekend and have a day to get past Monday morning face. We all get that that look on Monday morning. That look that says, I can't believe my weekend is over already and I am back in this place so fast.

    Tuesday seems to be pretty common, Microsoft's patch day as well. Gives you Monday to put any finishing touches/final review on things, then most of the work week with full support, development, etc. staff on hand. We've done a few Tuesday releases for that reason, though most of us involved work weekends too, it's good to have all hands on. This time around we finished everything of significance by the end of last week, I'm just wrapping up some loose ends this weekend which wouldn't have prevented us from releasing if we wanted.

    Many consider it to be a general best practice to not release on Fridays.
    https://stackoverflow.com/questions/2115612/why-not-to-deploy-on-a-friday
    http://www.saunderslog.com/2008/09/01/rule-1-dont-release-code-on-friday/



  • Hi!
    Its monday, will you guys make it cool one :)
    Hehe. When its ready… :)



  • 2.3 has 0 opened and 2.3.1 just had a bunch closed today.



  • I hope that (at least some of) bug fixes closed today still make into 2.3.0 for a polished product.

    Thanks for the hard work!  :)



  • Ended up having to rebuild release to address a couple issues. The minor GUI fixes that went into 2.3.1 today aren't going to make it, though we were tempted to merge them in, they're not significant and we can't keep making changes.

    We'll hopefully have a release in the morning.



  • If there was anything on the 2.3.1 list of issues that made it into the 2.3 release is there an easy way to tell?



  • Hmmm now I see 2.3.1.a.20160412.1112 but I have selected keep follow and switch to release.



  • The beta forum is gone (or archived)… so we must be really close!



  • ;D ;D

    The system is on a later version than
    the official release.

    Close?  It be done!



  • Just updated one system to 2.3-RELEASE

    Awesome job.



  • Good Job.  I am now on 2.3. Very smooth transition on the upgrade. I paused a video and resumed after the 3 min upgrade. No problems.

    Thanks Guys.



  • I can't wait to do this this weekend.



  • I had issues upgrading from RC to 2.3 release but I did a clean install in like 15 minutes I was back up and running.

    Thank you all who were involved in the project and getting 2.3 released. Well done guys. Very impressive release.