1
Citat
So there it is. Gone are the 2.6.<bignum> days, and 3.0 is out.
This obviously also opens the merge window for the next kernel, whichwill be 3.1. The stable team will take the third digit, so 3.0.1 willbe the first stable release based on 3.0.
As already mentioned several times, there are no special landmarkfeatures or incompatibilities related to the version number change,it's simply a way to drop an inconvenient numbering system in honor oftwenty years of Linux. In fact, the 3.0 merge window was calmer thanmost, and apart from some excitement from RCU I'd have called itreally smooth. Which is not to say that there may not be bugs, but ifanything, there are hopefully fewer than usual, rather than the normal".0" problems.
And as I already mentioned yesterday, I'm hoping the 3.1 merge windowwill be calm too, because due to the delays the latter half of themerge window will fall into my vacation time. I briefly consideredsimply waiting two extra weeks, but quite frankly, that wouldn'treally have solved anything (it would have made the merge windowinstead fall into LinuxCon and my divemaster weekends).
So I'm going to try to keep to the normal two-week merge window, butif it ends up being too busy for me to keep up, I may end up extendingthe window just so that I can merge everything. However, even if thathappens, that will *not* mean that I will accept big pull requests forlonger, it just means that I may end up delaying things to catch upwith timely merge requests.
That said, judging by past experience, the summer merge windows oftentend to be quieter, so maybe I worry needlessly. Much of Europe isstarting to go on vacation, and parts of the US are being fried to acrisp, so maybe 3.1 will be calm too.
Anyway, what has changed since -rc7 is mainly some RCU interactionswith the scheduler, and the RCU problems should hopefully be behindus. The pathname lookup race is also fixed. There's a few DRI fixes(i915 modesetting, and some Radeon fixes), and Al walked through somemore esoteric VFS d_lock issues. Other than that it's really prettysmall and random.
The shortlog from -rc7 is appended, the bigger "everything since2.6.39" list is obviously unmanageable.
This obviously also opens the merge window for the next kernel, whichwill be 3.1. The stable team will take the third digit, so 3.0.1 willbe the first stable release based on 3.0.
As already mentioned several times, there are no special landmarkfeatures or incompatibilities related to the version number change,it's simply a way to drop an inconvenient numbering system in honor oftwenty years of Linux. In fact, the 3.0 merge window was calmer thanmost, and apart from some excitement from RCU I'd have called itreally smooth. Which is not to say that there may not be bugs, but ifanything, there are hopefully fewer than usual, rather than the normal".0" problems.
And as I already mentioned yesterday, I'm hoping the 3.1 merge windowwill be calm too, because due to the delays the latter half of themerge window will fall into my vacation time. I briefly consideredsimply waiting two extra weeks, but quite frankly, that wouldn'treally have solved anything (it would have made the merge windowinstead fall into LinuxCon and my divemaster weekends).
So I'm going to try to keep to the normal two-week merge window, butif it ends up being too busy for me to keep up, I may end up extendingthe window just so that I can merge everything. However, even if thathappens, that will *not* mean that I will accept big pull requests forlonger, it just means that I may end up delaying things to catch upwith timely merge requests.
That said, judging by past experience, the summer merge windows oftentend to be quieter, so maybe I worry needlessly. Much of Europe isstarting to go on vacation, and parts of the US are being fried to acrisp, so maybe 3.1 will be calm too.
Anyway, what has changed since -rc7 is mainly some RCU interactionswith the scheduler, and the RCU problems should hopefully be behindus. The pathname lookup race is also fixed. There's a few DRI fixes(i915 modesetting, and some Radeon fixes), and Al walked through somemore esoteric VFS d_lock issues. Other than that it's really prettysmall and random.
The shortlog from -rc7 is appended, the bigger "everything since2.6.39" list is obviously unmanageable.
Linus
https://lkml.org/lkml/2011/7/21/455
Detaljer här: http://kernelnewbies.org/Linux_3.0
Det här inlägget har redigerats av JoWa: 21 maj 2012 - 04:12
3.0.0-8-kärnan här just nu.
