0 open issues 2.2 - does that mean a release is imminent?
-
To be fair… an RC kinda is a "testing for stability"-release
-
I'm aware of that, but the RC process has exposed a lot of issues which were fixed. Some major functionality wasn't even working during the RC until right near the end. In our process, once we reach zero bugs then we continue to test and wait for external testing reports from partners. Only after a short period (~1-2 weeks) with no more reported issues will we release.
-
We still have to test it internally, of course.
-
I'll not eat the minstrels just yet then. :P
Steve
-
@KOM:
In our process, once we reach zero bugs then we continue to test and wait for external testing reports from partners. Only after a short period (~1-2 weeks) with no more reported issues will we release.
That's effectively exactly what we've done. We've been down to 1 bug of consequence for a week, and one that we have full test cases to validate. That's been fixed for a couple days, and it'll be 3 or 4 more until we get through internal release testing, so end result is we'll be at 0 for near a week by release and only 1 for a week prior to that.
-
Seems 2.2-RC releases after 2015-01-16 is set for final release of 2.2 -> https://github.com/pfsense/pfsense/commit/6434d5be0cb450c5d70fedfd4cbdb232adf9d824
-
Yes, that's what Chris posted above..
-
small bug:
installation >> double "Accept and …." :)
http://i.hizliresim.com/mrXjlP.jpg
-
You should report bugs in https://redmine.pfsense.org/
-
small bug:
installation >> double "Accept and …." :)
http://i.hizliresim.com/mrXjlP.jpg
I see that as well, but if you press CTRL+L to refresh the view it cleans it up enough to select the right item.
Opened a ticket here: https://redmine.pfsense.org/issues/4241
-
@KOM:
I'm aware of that, but the RC process has exposed a lot of issues which were fixed. Some major functionality wasn't even working during the RC until right near the end. In our process, once we reach zero bugs then we continue to test and wait for external testing reports from partners. Only after a short period (~1-2 weeks) with no more reported issues will we release.
You're taking a snapshot from a brief moment in-time, and extrapolating. We're not ever going to wait for "zero bugs", because then we would never release. We've been in a highly-stable state for over a week now.
We've been testing like mad since October 2014. (I've been running 2.2 in various forms since April.) Testing occurred prior to this, of course, but the effort has been much more focused since October.
But yes, the 'cut' has happened. What started in October 2013 may finally release soon.
2.2 has been a long, difficult process. The move to FreeBSD 10(.1) (with the other changes that brought, such as unbound) is a huge step up, but has been challenging. When we started (Oct 2013), FreeBSD 10 wasn't even released, yet.
The move to strongswan (for a much better / more complete IPsec setup) has been challenging as well. The CARP re-write caused some issues. Even the AES-NI / AES-GCM work has required more effort than initially scoped. By contrast, the move to PHP-FPM was relatively painless.
Other than the internal testing, (and fixing anything critical it exposes) we're done with development for 2.2, and the focus is now on 2.2.1 and 2.3.
In particular, I'd like to fix the issues around IPV6 and 'pf' for 2.2.1 (as well as fix a plethora of other issues, all tagged 2.2.1 in redmine.) There are a handful of issues related to IPsec that are also targeted for 2.2.1.
We also have to fix the issues with PBIs. (At this point, nobody else in the FreeBSD world uses them.)
-
We also have to fix the issues with PBIs. (At this point, nobody else in the FreeBSD world uses them.)
The computer industry!!! Some whole new sub-system gets put into a product, supposedly the new and great thing, then a few years later is dumped for something else (or for going back to what was before). There is masses of effort from thousands of computer geeks porting these things and then removing them - I guess it is just a plot to keep us off the streets and out of trouble.
-
Well seems after I reboot my sshd server stops running is this only my issue or is anyone else having?
-
Well seems after I reboot my sshd server stops running is this only my issue or is anyone else having?
I have not had trouble with sshd. You would be best to look in System Log and see if there are any interesting messages, then post a new thread - problems will get lost if they are mixed in this thread.
-
Well seems after I reboot my sshd server stops running is this only my issue or is anyone else having?
I had. Not only sshd, but radvd and possibly even something that depends libdaemon.so.0. Removing squid3 and lightsquid solved the problem.
-
I guess it is just a plot to keep us off the streets
Packs of coders roaming wild. Sounds dangerous. ;)
-
Well seems after I reboot my sshd server stops running is this only my issue or is anyone else having?
I too am having this problem and troubleshooting through the command prompt feature has been rough. I'm also not getting any further updates which I attribute to the recent freeze.
No working transparent proxy, no ssh and no updates has me in a but of a lurch to get this sorted.
I was going to wipe and reinstall this weekend but ran out of time. Fingers crossed for time on Thursday night.
-
Please do not post problems in this tread, post them in their own separate thread.
-
We also have to fix the issues with PBIs. (At this point, nobody else in the FreeBSD world uses them.)
fix or move to something else/better :)
This will be on 2.3 ou 2.2.1?
-
We also have to fix the issues with PBIs. (At this point, nobody else in the FreeBSD world uses them.)
fix or move to something else/better :)
This will be on 2.3 ou 2.2.1?
2.3
The pkg system on FreeBSD has matured a lot since we used packages before, things should be much easier to manage without the problems we had in 2.0.x and before with the UNIX-equivalent of "DLL hell" that we hit frequently. PBIs were a good move at the time, but not so much anymore.
