2.0.2 ???



  • @cmb:

    Not sure how you even got to 2.0.2, it's not supposed to be available for anyone other than us.

    It was made clear months ago that 2.0.2 was not intended for public consumption at the time.
    It went from rc1 to rc2 to rc3 to rc4 to 2.0.2 Release….and then it vanished.

    But not a peep.
    Not a word in the forum.
    Not a press release.
    Not a hint.
    Not a word anywhere.

    2.0.2 release is excellent!
    It has behaved even better than 2.0.1 release for me.

    I have no doubt that the PFSense group has a very good reason for the things it does.

    Is it reasonable to ask why that reason is such a secret?
    NOT what the reason is.  Just why it's such a big secret.



  • I heard there was a place if you searched hard enough for it. Personally, I have it cause I have a build environment and I built it once JimP incremented the version.
    I have only installed it in the Lab for some testing.

    BTW … a BIG thanks for all the work put into making this a great open source project.



  • we have some things going on behind the scenes at the moment that is taking up a lot of our time. It'll come as soon as we have time.



  • No rush. I think it is better to take your time and get it perfect than to rush and miss something. Again, thanks for all you guys do!



  • "behind the scenes"

    Hmmmmm….let me guess.
    Have anything to do with money?


  • Rebel Alliance Developer Netgate

    Nope, just time! The images are actually built and ready to go from a technical standpoint, there's just a bunch of hoopla to go through (signing the images, pushing them to the servers, preparing the release announcement, and so on) that we haven't had time to wrap it up all the way because of other things going on.

    They'll be up soon :-)



  • When the developers are busy, this is can be good thing. Just have patience, they will get it released.


  • Rebel Alliance Developer Netgate

    Oh it's nothing bad, just lots to do, on the commercial support side and on the personal side.



  • @podilarius:

    When the developers are busy, this is can be good thing. Just have patience, they will get it released.

    Pod….The original inquiry wasn't inspired by impatience.

    2.0 was developed in the light of day.
    Builds were systematically made available as procedure.
    Downloading and evaluation was encouraged.
    Issues were discussed and bug reports solicited.
    The RC's were openly and widely discussed.
    And the "Release" remained available just like all the builds that preceeded it.

    2.0.1 was developed in the light of day.
    Builds were systematically made available as procedure.
    Downloading and evaluation was encouraged.
    Issues were discussed and bug reports solicited.
    The RC's were openly and widely discussed.
    And the "Release" remained available just like all the builds that preceeded it.

    Then something changed.

    From it's beginning 2.0.2 was unannounced, not discussed nor made public.
    And when it reached "Release" status it disappeared.

    As the original post indicated, the PFSense group has very good reasons for the things it does.
    The decision to develop 2.0.2 in the dark was made some 4 or 5 months ago.
    It's not likely that a surge in activity today was the reason for a policy decision made months ago.


  • Netgate Administrator

    That's an interesting point you make.
    From what I understand 2.0.2 is/will be a bug fix release so perhaps extensive beta testing was not required. By the time 2.0.2 was on the cards 2.1 was being actively tested with daily snapshots. Only a few months ago it was hoped that 2.1 would be released in time for IPv6 day and then by BSDCan. However this didn't happen and personally I'd much rather it was delayed than released with bugs. However I've inferred most of this so I'm open to correction!  ;)

    I can see how having both 2.0.2 and 2.1 in beta testing could cause endless confusion.

    Steve


  • Rebel Alliance Developer Netgate

    Actually 2.0.1 wasn't all that public either, since there was a security vulnerability announcement involved.

    The commits and such for 2.0.2 have always been out there, the snapshots were even there if you know where to look, it's just not very exciting compared to people talking about 2.1 ;-)


  • Rebel Alliance Developer Netgate

    And yes, 2.0.2 is a maintenance release, so changes are fairly minor, though there are some more significant things in there (like the NTP changes).


  • Netgate Administrator

    Looks pretty exciting to me.
    Particularly switching ntp daemon.  ;D
    Thanks Jim.

    Steve



  • @Pennyless:

    Pod….The original inquiry wasn't inspired by impatience.

    Most of the time a post like this is made with a little inspiration from a lack of patience.
    2.0.1 was not widely known at all. You had to be watching github to even know it was being worked on. There were snapshots, but everyone who was on the release didn't know about it from the autoupdate but had to go to the snapshot server. 2.0 got the same attention that 2.1 is getting.
    With 2.0.2, it is basically the same without the snapshot server having the images. You could still watch github for the changes. I didn't know where to look to get the snapshots, but that is okay, I am testing 2.1 not 2.0.2. For the few system I have running 2.0 series only one is a "lab" machine and the rest are production. I am not loading snapshots on production firewalls.
    Like I said, I did have a build server to create my 2.0.2, and those who knew where to get it got it and was helping test. I saw a few posts in the forums about 2.0.2. I don't really watch the mailing list, so I am not sure about it being there or not.
    I am not sure about the disappearance. Perhaps they needed the space back for 2.1 snaphots. If that is the case, then more 2.1 please.
    Just because you didn't know where to find the light does not mean the rest of us were in the dark about 2.0.2.


  • Rebel Alliance Developer Netgate

    The 2.0.2 snapshots were up while it was actually doing snapshots. Now that the release images have been built, they are shut down (as we always do close to a release) to avoid having someone out there with a build labeled "2.0.2-RELEASE" that is not actually the release. If we find something that needs fixed, their now outdated image wouldn't know it needed updated.

    So at the moment we're just doing what we've always done… It's just a little delayed due to lack of time to get it all in place.



  • Thanks JimP, I stand correct on the snapshots for 2.0.2.
    There is not rush to get 2.0.2 out. Take your time. Thanks for all your efforts building and support this great project.


  • Banned

    When will it be released Jim and thanks for the brilliant work so far!


  • Rebel Alliance Developer Netgate

    As I said earlier, very soon, as soon as we have time to finish up the whole release process.



  • Has there been any movement on a 2.0.2 release? Will it be out before 2.1, which is supposed to be out very soon itself?


  • Rebel Alliance Developer Netgate

    There really isn't anything holding back 2.0.2 still, just time.
    2.1 has plenty of things holding it back.



  • Hi,

    Is there any milestone or timeline for pfSense project?


  • Rebel Alliance Developer Netgate

    We don't keep one officially, but redmine tracks it:
    http://redmine.pfsense.org/projects/pfsense/roadmap

    We never did have an official entry/designation for 2.0.2 in there.



  • As I indicated in the original post.
    2.0.2 release is exceptional.
    My system runs dual quad xeons, has 26 nics comprised of 12 low bandwidth ISP's balanced into one tier and numerous servers and appliances attached to the remaining 14 nics.
    It is a very busy system, and not so much as one hickup, belch, burp, or f*rt.
    It has performed even more error free than did 2.0.1 which was excellent.
    I have the last (I guess you would call it pre release - release) 2.0.2 iso before it was taken down.
    I have no idea what's really going on here, but if you want the last version that was in the public domain let me know.


  • Rebel Alliance Developer Netgate

    As I've said, we have the images, it's mostly that the right people haven't had enough time to get the release formally signed and rolled out.

    Actually I found a couple more issues with the images today, and also added a warning about PPTP being compromised (not specific to pfSense, PPTP as a whole has been cracked), so there will be another round of new images.


  • Banned

    How has PPTP been cracked??


  • Rebel Alliance Developer Netgate



  • @jimp:

    2.1 has plenty of things holding it back.

    Isn't 2.1 supposed to be out by 18th October, in time for EuroBSDCon 2012?


  • Banned

    Dont think it will happen….



  • @Supermule:

    Dont think it will happen….

    That's a shame. I was really looking forward to it. From an outside perspective, it looks almost like the pfSense project is grinding to a halt…


  • Banned

    From my POV, then v.2.0.1 has taken steps in the wrong direction regarding user friendlyness.

    Its very obvious that it is nerds that has designed the GUI and you have to do a lot of manouvering in the menus to accomplish basic tasks.

    2.0.1 also has the disadvantage that it consumes a lot of CPU running virtualized as many do now a days.

    If you colocate and pay by the CPU use, it could get expensive in the end. 1.2.3 doesnt have these issues at all.

    You see a lot of help done here on the forums that comes down to a not so intuitive user interface.

    It could be a lot better!

    I look forward to 2.0.2 since the ISO tested didnt perform as well as 1.2.3 and NAT was unstable in reflection state.

    I hope this is solved in 2.0.2. Otherwise 1.2.3 will stay a little longer.


  • Rebel Alliance Developer Netgate

    @ingmthompson:

    That's a shame. I was really looking forward to it. From an outside perspective, it looks almost like the pfSense project is grinding to a halt…

    If someone only watches the blog, maybe. But anyone taking even a passing glance at the forum, github, redmine, etc, can see there is constant activity.

    @Supermule:

    From my POV, then v.2.0.1 has taken steps in the wrong direction regarding user friendlyness.

    Its very obvious that it is nerds that has designed the GUI and you have to do a lot of manouvering in the menus to accomplish basic tasks.

    2.0.1 also has the disadvantage that it consumes a lot of CPU running virtualized as many do now a days.

    If you colocate and pay by the CPU use, it could get expensive in the end. 1.2.3 doesnt have these issues at all.

    You see a lot of help done here on the forums that comes down to a not so intuitive user interface.

    It could be a lot better!

    I look forward to 2.0.2 since the ISO tested didnt perform as well as 1.2.3 and NAT was unstable in reflection state.

    I hope this is solved in 2.0.2. Otherwise 1.2.3 will stay a little longer.

    Not sure how the 2.0.x GUI is all that different from 1.2.3 in the way you describe. Main difference is the dashboard but that has nothing to do with navigating from page to page. In 2.1 I've made navigation quite a lot easier with the shortcut bar that lets you easily move between pages in the same "section" such as if you're looking at DHCP settings, you can see the service status right on the page, go to the logs, leases, etc. without digging through the menus to find the other entries.

    I've not heard of 2.0.x using more CPU than 1.2.3 in general, and we have a ton of customers running 2.x in production environments colocated/virtualized.


  • Banned

    Many are reporting extensive use of CPU on host running 2.0.1 virtualized….


  • Rebel Alliance Developer Netgate

    Where? I don't recall seeing them, but then I don't watch the virtualization part of the forum all that closely. I don't recall any of our customers complaining though.

    The only CPU-based complaints I remember are people who had polling enabled and didn't understand what it really was/did and didn't need it. They believed they were maxing out their CPU all the time when in reality that's just how polling works and reports CPU usage, it just changed how visible that was to the user, it didn't actually change the amount of CPU used.


  • Banned


  • Banned

    First hit on Google….


  • Rebel Alliance Developer Netgate

    Ah, seems there are a few people in there (not just esx, but kvm, proxmox, etc) having the issue and some also not seeing any issue at all. Difficult to tell from that if it's their hardware, something specific to FreeBSD/pfSense, or if it even was the same behavior on older versions. Not really enough data there to point a finger in general. It's certainly not happening on any of our ESX gear that we run. That's more suited for that other topic, not here though.


  • Banned

    Thx Jim!


  • Rebel Alliance Developer Netgate

    Also I wouldn't expect 2.0.2 to be any different - same base OS as 2.0 and 2.0.1.

    2.1 might be different.



  • @ingmthompson:

    That's a shame. I was really looking forward to it. From an outside perspective, it looks almost like the pfSense project is grinding to a halt…

    Well, the overall development activity (github commits & addressing of open issues at redmine) during past 6 months, does appear to be at a much lower level than the same period last year (while working on v2.0) …


  • Rebel Alliance Developer Netgate

    Last year at this time we were finalizing the 2.0 release, which was huge, and there were a lot more issues (especially with upgrades) that makes it hard to compare against, plus it was in the late RC stage. At the moment we are addressing things but the main problems are quite deep down in the OS/Kernel mostly, so there aren't as many people that can hack on those parts.

    Once we get over a couple hurdles there and do an official BETA release of 2.1 activity will likely increase as more things get noticed that everyone can work on.


Locked