Thanks to the developers!
-
+1
And this is not always hate, it's bug report which helps devs to fix mistakes. I agree that some people could learn how go talk respectfully, but I feel devs are clever, they don't take it to heart.
-
Yes, thank you from me too.
My only criticism is that 2.3 should have been called 3.0.
It is obvious that a lot of work went into this release and it's been unnecessarily concealed behind a minor version number increment. I refer to it now as 2.THREE so that the point release might get the recognition it deserves.
Looking forward to the NUT package release. -
+11
-
It is obvious that a lot of work went into this release and it's been unnecessarily concealed behind a minor version number increment.
What rock have you been living under? This things been in public beta for months. Good lord there was even a section of the forum dedicated to it for discussion on it that anyone was able to participate in. And that doesn't even address github contributions….....
I don't know how much more transparent you can get that that.
-
It is obvious that a lot of work went into this release and it's been unnecessarily concealed behind a minor version number increment.
What rock have you been living under? This things been in public beta for months. Good lord there was even a section of the forum dedicated to it for discussion on it that anyone was able to participate in. And that doesn't even address github contributions….....
I don't know how much more transparent you can get that that.
I'd wager only a tiny fraction of users ever come to the forums. Most just wait for the New Update Available button to appear, and then click it.
It would probably help if that section of the admin UI let the devs vend a live URL to at least a blog post or FAQ when warranted, as was definitely the case for this major update.
-
It would probably help if that section of the admin UI let the devs vend a live URL to at least a blog post or FAQ when warranted, as was definitely the case for this major update.
Yes, that would be a useful addition - so that when you click through to the update screen, there is a link displayed to the release notes. Maybe then more people might go read the release notes before pressing the update button.
-
What rock have you been living under? This things been in public beta for months. Good lord there was even a section of the forum dedicated to it for discussion on it that anyone was able to participate in. And that doesn't even address github contributions….....
I don't know how much more transparent you can get that that.
I have been living under a 16hr day, 7day a week running-my-own-small-business rock. I didn't have time to participate in beta testing this version although I have done so on previous versions.
I don't dispute what you say about the openness of development. In my opinion, the amount of work put in by the developers should have been credited with a 3.0 version number. A version increment from 2.2.6 to 2.3 doesn't appear to be a significant change for most admins not following the day-to-day development progress of pfSense.
-
I just wanted to say thank you, also! Initial upgrade was terrible. Turned out my usb drive died during the upgrade. Replaced it with a fresh install, checked permanent RW and disabled update check and its silky smooth. Love the new theme. Keep up the great work!
-
The change from 2.2.x to 2.3 helped me succeed with an installation onto a Dell Optiplex GX520 SFF Celeron. It looks like the installer now takes Dell mobo weirdnesses into consideration. Before I was getting this error:
launching installer ncurses front end … /scripts/lua_installer: /usr/local/sbin/dfuife_curses not found. Installation did not finish correctly (Then a "99" selection for install appeared in the list, which didn't work.)
An .iso of 2.3 was all that was needed. Install complete! Thanks to whomever!! (The "99" selection is now gone from the list - probably since at that point, it isn't needed due to the successful load.)
-
It would probably help if that section of the admin UI let the devs vend a live URL to at least a blog post or FAQ when warranted, as was definitely the case for this major update.
We are considering putting text on the Update page that mentions reading the release notes / upgrade guide and linking to them.
…possibly even a checkmark that says you have read them before proceeding with the update :P
-
…possibly even a checkmark that says you have read them before proceeding with the update
It could even ask a few questions about the content of the release notes and only let you upgrade if you get the answers right. :-\
-
BIG +1
-
…possibly even a checkmark that says you have read them before proceeding with the update
It could even ask a few questions about the content of the release notes and only let you upgrade if you get the answers right. :-\
Why not? We are a dealer that sells a product in which we have to do this very kind of thing if we want to keep selling the latest and greatest.
