PA4 testing results

[Wolfgang Romey]

Am Donnerstag, 15. August 2013, 16:27:14 schrieb Thomas Pfeiffer:
> On 15.08.2013 12:52, Sebastian Kügler wrote:
> > Hi Thomas,
> > 
> > On Wednesday, August 14, 2013 23:36:07 Thomas Pfeiffer wrote:
> >> I finished testing standard scenarios in PA4.
> >> I've found two bugs which I would not advise to release with:
> >> - The PMC problem (see previous mail). The fix is there, it just somehow
> >> isn't  in the package on this image
> >> - The Rating filter seems completely broken (
> >> https://bugs.kde.org/show_bug.cgi?id=323512 ). If that's not fixable, it
> >> should  be removed/hidden in PA4. It's not like this is a very important
> >> filter, but when you tap a star and it does precisely zero, that gives a
> >> very bad experience
> >> 
> >> Other than that, I could not find any completely broken features or other
> >> serious problems. If these two are fixed or worked around, PA 4 is good
> >> to
> >> go  from my side!
> > 
> > But you have to promise to not find showstoppers once these are fixed!
> 
> I have already finished testing yesterday (and found no other
> showstoppers than these two), so if the bugs are fixed without the fixes
> causing more trouble somewhere else, I won't bother anyone anymore for
> this release.
> 
> > Seriously, we need to get it out. We'll always be able to find more things
> > that need (really need!) fixing. But, as Aaron said: "If a project doesn't
> > release, it dies". So we have to take our pride and reuse it for the next
> > release.
> 
> I confined myself to mentioning only those bugs that I think would have
> a significant negative effect on the early experience.
> 
> It might be comparing apples and oranges, but if I look at the game
> industry, for example, companies that tend to delay a release to improve
> its quality have a way better reputation with gamers than those that
> release very buggy games and ship big bugfixes during the first few weeks.
> 
> That does not mean we should imitate Duke Nukem Forever, of course ;)
> 
> > Also, we can ship bugfixes to a released version.
> 
> True, but see above.
> 
> I am the quality coordinator, and I perceive it as one of my duties to
> be the advocate for quality. In this role, my priorities are different
> than yours, but I think that's a good thing: By negotiating between our
> positions, we can arrive at a good balance between quality and
> time-to-market.
> 
> I'll retest the two problems with the newest image as soon as I get
> home, I assume they're gone then, and I'll be all green lights for
> releasing.
> 
> 
> _______________________________________________
> Active mailing list
> Active at kde.org
> https://mail.kde.org/mailman/listinfo/active

Hi Thomas,

thank you for testing so thoroughly and Marco for fixing the bugs so fast.

Wolfhgang
-- 
Wolfgang Romey

Anhänge bitte nur in offenen Formaten wie z.B. die openoffice-Formate

Diese email ist signiert.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/active/attachments/20130815/f9b526f4/attachment.sig>