Comment 9 for bug 64488

> Therefore, I am curious what criteria you used when determining what
> would prevent distributions (including Kubuntu) from updating to 1.0.1

1) Don't break string freeze.
2) No dependency changes.
3) Sucessful build tests on the same fairly large variety of platforms and systems that 1.0 underwent (Linux, Mac OS X, FreeBSD; gcc 3.4 - 4.2; KDE 3.4 and 3.5; x86, amd64 and PPC -- some of those tests were done by Kubuntu personnel and therefore on Kubuntu systems, including Edgy).
4) Peer-review all code changes.
5) Confirm bugfixes with the original reporters, where available (example: the aforementioned 'media' script failing to connect to Amarok when the Amarok ReplayGain third-party add-on was installed was reported by CVS-Digest.org author Danny Allen and fixed to his satisfaction).

> However, bear in mind that if you discover a problem with 1.0.1, you solve
> it quickly and easily by testing and releasing a 1.0.2 tarball.

There's no doubt that the scope of the release preperations for a distribution is larger vs. a single application. Since we don't exactly just tar it up and push it out without thinking twice either (as outlined above), I'm aware of the penalty incurred by having to abort and restart the process, albeit on a smaller scale. FWIW, there have been no new defect reports since the release of 1.0.1 on October 6th in our own bugtracking system (KDEs Bugzilla) nor in our IRC channel (a fairly popular feedback medium considering it's an IRC client). Note that there were five weeks between 1.0 and 1.0.1; 1.0.1 was not rushed.

> I hope that I've adequately explained the need to be conservative in making
> changes to the distribution at such a late hour.

You have, and I am certainly understanding of your position. There won't be any hurt feelings if Kubuntu 6.10 ships without Konversation 1.0.1 on our end; Konversation 1.0 is a fine and mature piece of software. Konversation 1.0.1, however, is better software in the aspects listed in the initial report, and my persistence is motivated by the belief that it can provide a significantly better experience to Kubuntu users.

As for the format of this exeption request not conforming to Kubuntu/Ubuntu regulations, that is unfortunately beyond my control. What I can do is provide information about the release.