It DOES compile. The issue, the author was refering to, is already sorted out. Don't worry, the mail is just the usual occurence of panic close to releases.
The mail was a rant from 3 core-developers who don't feel compfortable about the changes to the "release-policies", made for the 3.0-cycle. It sure helps to see the disadvantages of a procedure to optimze it. That's, what is happening in the thread on the list right now and it's not even worth a slashdot-message, because it's absolutely no big deal. KDE will not suffer from it, quite the contrary, work-processes gain much, if the workers are capable of constructive criticizm.
Well, there is one advantage of the digital projectors, the framerate. This can be important in fast moving scenes, i.e. the "explosion" of Sauron in the LotR would have been improved, the creators were forced to add much blur to produce a effect of fast moving. This could have been much sharper with higher framerate.
Slashdot Mirror
Because, you didn't help the packagers?
It DOES compile. The issue, the author was refering to, is already sorted out. Don't worry, the mail is just the usual occurence of panic close to releases.
The mail was a rant from 3 core-developers who don't feel compfortable about the changes to the "release-policies", made for the 3.0-cycle. It sure helps to see the disadvantages of a procedure to optimze it. That's, what is happening in the thread on the list right now and it's not even worth a slashdot-message, because it's absolutely no big deal. KDE will not suffer from it, quite the contrary, work-processes gain much, if the workers are capable of constructive criticizm.
Well, there is one advantage of the digital projectors, the framerate. This can be important in fast moving scenes, i.e. the "explosion" of Sauron in the LotR would have been improved, the creators were forced to add much blur to produce a effect of fast moving. This could have been much sharper with higher framerate.