--===============0519216901911622928==
Content-Type: multipart/signed;
  boundary="nextPart1447968.io7Nsy9hzO";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1447968.io7Nsy9hzO
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear release team,

I upgraded a few days ago from 4.6.5 to 4.8-RC1 and worked with it some tim=
e.
As I'm a big KDE advocate, I'm currently having a deep feeling and fear that
quality assurance is currently missing.
Please do not take this as a rant but as a fear for releasing software whic=
h is
not in a releasable quality state.
I just used this "Release Candidate 1" for a few days in the usual way I
used the software colledtion before for a lot of years (I mean: not doing w=
eird
things or testing extreme cases)
but I since have only detected regressions (mainly in khtml)! and this is t=
he reason I
felt the urge to write to this mailing list, as I want to avoid that KDE in=
 the
current situation is released to the wild. I have the strong feeling that
this would leave a very bad impression to a lot of users.
(And I can not remember any RC version with that many regressions I found in
just a few days)

=46or software in a "beta" stage this would be ok, but as I read that
TODAY the software collection is going to be tagged as RC2, I strongly advi=
ce
against naming it a release candidate!
Please let the developers take some additional time to fix the most annoying
regressions before releasing.
Probably you could motivate the developers for a "bug fixing week" before
the tagging or some other way of QA.

I'm a professional software developer since > 20 years, and I would never
release software in such a state.

Again: this is no rant! I'm just looking for damage limitation as I love KDE
and I'd like to be able to recommend KDE to other people as well.

The details (regressions) I found in the last 3 days:
https://bugs.kde.org/show_bug.cgi?id=3D290375
https://bugs.kde.org/show_bug.cgi?id=3D290373
https://bugs.kde.org/show_bug.cgi?id=3D290371
https://bugs.kde.org/show_bug.cgi?id=3D290331
https://bugs.kde.org/show_bug.cgi?id=3D290324
https://bugs.kde.org/show_bug.cgi?id=3D290278 (probably already fixed)
https://bugs.kde.org/show_bug.cgi?id=3D290276
https://bugs.kde.org/show_bug.cgi?id=3D290274 (very serious!)
https://bugs.kde.org/show_bug.cgi?id=3D290273
https://bugs.kde.org/show_bug.cgi?id=3D261325 (new problem added)
=2D-=20
Best regards/Sch=F6ne Gr=FC=DFe

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail=20
/\  www.asciiribbon.org   - against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.bibibest.at

--nextPart1447968.io7Nsy9hzO
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iD8DBQBPAXkSHmdPoI37D4YRAlawAKCL2Mj3LcBs5WApM48YQBsOvfJT/gCbBJUe
kUlA7laGDCXZ0rEY7fix/TI=
=3QN1
-----END PGP SIGNATURE-----

--nextPart1447968.io7Nsy9hzO--

--===============0519216901911622928==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

--===============0519216901911622928==--