SOP for errata?

[Aaron J. Seigo]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi all..

in the last two weeks it's come to my attention that upgrading to Qt 3.1.2 
will cause KsCD to crash on startup if remote CDDB requests are enabled for 
may (though not all) users. the quick solution seems to be to downgrade to Qt 
3.1.1 or turn off remote CDDB requests.

i have yet to come up with a patch to fix this properly (or even investigate 
the actual source of the problem, beyond that it's a socket timing problem in 
KsCD's logic), but i plan to replace the offending code completely with 
libkcddb.

in any case, in between now and then, for everyone who has a stable KDE3 
install and then upgrades to Qt 3.1.2 they may end up with a crashing KsCD. 
since i've received a number of reports on this now, i was wondering:

is there a standard operating procedure for releasing KDE related stability 
errata?

i know there is a general procedure for security errata, but have yet to see a 
stability errata released. i'd like to keep the users happy by giving them a 
heads up on this one, but am unsure the best way to do this. i could simply 
put a page up at a website somewhere and submit it to theDot?

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE: The 'K' is for 'kick ass'
http://www.kde.org       http://promo.kde.org/3.1/feature_guide.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+lIKP1rcusafx20MRAmkuAJ9skwCnVgmD1X9m9Drwo+RKUZsbDQCgo9r2
r93RI2sODBNeg6+tdv9E+mI=
=JIB/
-----END PGP SIGNATURE-----