[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-active
Subject:    RE: Lessons for PA3
From:       "Thomas Pfeiffer" <colomar () autistici ! org>
Date:       2011-12-16 13:57:12
Message-ID: 003101ccbbfa$9c5d9aa0$d518cfe0$ () autistici ! org
[Download RAW message or body]

> I'm actually thinking of something like a week between code freeze and
> release. With a longer cycle (7 instead of 2 months), that's relatively
> bearable, I tend to think -- and really, having everything ready two
days in
> advance doesn't really hurt anyone, or does it?)

What about betas and RCs? As PA grows, I don't think we can rely on
ourselves to do
all the testing, so why not do it like most FOSS projects I know do?
I know those cost extra time, but I'd still prefer to do them. We don't
need to
start shipping the first beta months before release, but maybe a few weeks
of public
testing could already help?

Plus there is another thing we should definitely do with PA3: Proper
upgrade tests.
Things like https://bugs.kde.org/show_bug.cgi?id=289103 , could be avoided
if there was enough time to do a as-realistic-as-possible upgrade test
before release.

Apart from that, I agree with all points brought up so far. I'd prefer
waiting
longer until the next release if the quality is better and even as a
non-developer I
feel awkward about doing many patches to kdelibs and kde workspace, so
synching with KDE SC sounds like a good idea to me as well.

Regards,
Thomas

_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
[prev in list] [next in list] [prev in thread] [next in thread]