Update available. Click Here to play Russian Roulette
-
Is there any changelogs for every build?
I mean a some kind of a "generic" changelog – nor buildlog nor cvs diff :) nor any similar but just a list of areas to be more close with. For example "now parsing a floating rules happens at stage X after Z not Y like before". This helps many non-devel but experienced users to pay more attention not to all and every but to a specific operations and their results and therefore helps to fight bugs more quickly.
-
the commit logs at rcs.pfsense.org have exactly what is changed.
-
cmb, thank U, am I right that U mean a https://rcs.pfsense.org/projects/pfsense didn't it?
Also more on topic:
- anyway didn't find any way to view AIO like a somekind of a "dijest" – is it here somewhere?
- IMHO if it's here than an "Updates" page of a WebUI should show a link to the such "dijest" somewhere -- in the same textarea with "A new version... Current... New..." for example instead of "update source:..."
-
Updated 2.0-02.02.2011 to 2.0-04.02.2001.midnight and got```
Packages are currently being reinstalled in the background.
Do not make changes in the GUI until this is complete.Then after a few hrs I C this "Update available" again. Well, updated again (2.0-04.02.2001.midnight > 2.0-04.02.2001.daily :)) and got the same``` Packages are currently being reinstalled in the background. Do not make changes in the GUI until this is complete.Fortunately the only Squid-2 been installed so it doesn't taken many time…
Is there been a real changes that really needs to reinstal packages?!
Why not make just a WebUI "Acknowlegement"?! -
Why not make just a WebUI "Acknowlegement"?!
Because screwing around with the config while packages are reinstalling can blow things up. If a package has an issue that it doesn't reinstall, the package needs to be fixed.
-
@cmb:
…with the config while packages are...
Sure but I mean something like a msg "System updated, pls reinstall Ur pkgs, click here to do it" – exactly like an "Update available. Press here" looks and works.
-
@cmb:
the commit logs at rcs.pfsense.org have exactly what is changed.
Unfortunaly it is NOT what I'said about: @me:
nor buildlog nor cvs diff Smiley nor any similar but just a list of areas to be more close with
Compare a recent (for a week for example) posts in this subforum and a descriptions on the RCS site u've pointed to – here is nothing close.
Take for example a recent topics abt a forced packages reinstalling (it's not best but only first example) or something simmilar. What on RCS descriptions can predict this behaviour? Nothing. Well, well, something can, but this "something" understandable for those who are very tight to a pfSense (nor bsd nor anything else but exactly pfSense) internals only. And this very narrows a circle of potential debuggers – not "unsatisfied users" but debuggers :)
-
Take for example a recent topics abt a forced packages reinstalling (it's not best but only first example) or something simmilar. What on RCS descriptions can predict this behaviour? Nothing.
Wrong - "Reinstall packages on bootup during console. Ticket #1156" is about as clear as you can get. That's the commit log from the change that brought that back on January 5. Almost all of the commit logs are clear whether or not you understand the actual source changes.
We're not going to write up a change log on every single commit, we just don't have time for that, those who follow snapshots have to read the commit logs themselves or take chances. Official releases and RCs come with change logs.