>Darrell spent some time to write about outstanding issues. Not 
>many fortunately.
>
>What exactly is allowed on the source code after RC1 is tagged? 
>Are we restricted to critical bug fixes and nominal patches, or we 
>still have a good degree of freedom?
>Actually this is a question I have been asking myself for a 
>while....

Good question. What does RC status mean?

>As Darrell said, I am working on bug 1825, which although not a 
>blocker, messes up all documentation indexes, so IMO should be 
>resolved before releasing R14 (even though technically a fix could 
>be push even after RC1 is tagged).

I'm working hard on updating the handbook system. The handbook 
system is an utter mess. No, an embarrasing mess, having been 
ignored since about KDE 3.2.

I would like to see 1850 fixed for R14, although that has been 
broken since KDE3 days.

There is a lot of handbook work to do for a long time. We have an 
etherpad of most handbook issues:

http://trinity.etherpad.trinitydesktop.org/82

I have no illusions about fully mending the handbook system for 
R14. R14 won't crash or disintegrate without additional handbook 
attention, but I'd like to finish the foundation work and my list 
in that respect shrinks daily.

We get only that one proverbial chance to release R14 as a polished 
release.

Darrell