The third beta of FreeBSD 7.0 has been released. I cannot seem to find any information on changes between the second beta and this one. Additionally, the release schedule doesn't even list a third beta.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-07-15
Nice story, but did you actually read any of the mailing lists?
>The last minute import of a few things caused RELENG_7 to regress in alot of places.
This is absolute nonsense! Neither there were last minute imports nor is there regress in *a lot* of places.
Everybody can read it of course,
http://lists.freebsd.org/pipermail/freebsd-stable/
http://lists.freebsd.org/pipermail/freebsd-current/
http://lists.freebsd.org/pipermail/cvs-src/
> if showstoppers keep popping up out of nowhere like they have been, it won't be the case.
Huh? Maybe you should start your urband legends in kindergarten. There are of course *bugs* but hardly showstoppers. If you're a tester, you should maybe check your hardware first.
Member since:2005-07-06
Member since:2007-11-20
yes, and I have talked to a number of freebsd developers and core team members; it's normal for people to import things into HEAD just before a new -STABLE branch is made.. There's a rush of developers importing things from their perforce branches so it can make it into 7-STABLE and not be stuck in 8-STABLE (when it gets branched.)
The gcc 4 import set things back considerably, this is a fact. There were enough breakages to cause re@ to wait until another version was released that would fix the bigger bugs.
There are regressions in various drivers, particularly the NIC drivers (as they were removed from being under the GIANT lock), and some with regards to interrupt filtering. There is also strange panic and segfault conditions that arise at seemingly random times. As an example, a panic on sysctl, panics with acpi states. If you'd like, look at the pr database.
The biggest problems seem to be the ones that can't be reproduced after they happen. Since dumpdev is off by default there is no kernel dump so nothing to go on other then 'it paniced'.
They are being fixed, of course, when they come up, but 6.3 is still a possibility for being released before 7.0.
Member since:
2007-11-20
The last minute import of a few things caused RELENG_7 to regress in alot of places. The quick builds are because it's still not known if 6.3 or 7.0 will be released first. The goal being to get 7.0-RELEASE out before January 1st, if showstoppers keep popping up out of nowhere like they have been, it won't be the case.