On Fri, Jun 22, 2012 at 1:27 AM, Aaron J. Seigo wrote:
> On Thursday, June 21, 2012 20:17:50 Martin Gräßlin wrote:
>> if there is interest in the team, I am willing to do the administrative work
>> of creating target milestones and disabling outdated ones. I'm doing that
>> work for kwin anyway an
On Thursday, June 21, 2012 20:17:50 Martin Gräßlin wrote:
> if there is interest in the team, I am willing to do the administrative work
> of creating target milestones and disabling outdated ones. I'm doing that
> work for kwin anyway and doing it for Plasma would not create much work.
cool! than
On Thursday 21 June 2012 17:45:20 Aaron J. Seigo wrote:
> On Thursday, June 21, 2012 17:18:15 Martin Gräßlin wrote:
> > next. That might work also for Plasma.
>
> we have done this in past releases. it does work. i'd like to do it again.
> but it takes effort, leadership and group cooperation.
if t
On Thu, Jun 21, 2012 at 5:43 PM, Aaron J. Seigo wrote:
> On Thursday, June 21, 2012 16:13:32 Mark wrote:
>> think we should make releases with random pieces cutted out, or they
>> will never be complete" so we don't cut out pieces that don't work yet
>> we also don't want to release pieces that do
On Thursday, June 21, 2012 17:18:15 Martin Gräßlin wrote:
> next. That might work also for Plasma.
we have done this in past releases. it does work. i'd like to do it again. but
it takes effort, leadership and group cooperation.
--
Aaron J. Seigo
signature.asc
Description: This is a digitally si
On Thu, Jun 21, 2012 at 5:18 PM, Martin Gräßlin wrote:
> On Thursday 21 June 2012 16:56:51 Marco Martin wrote:
>> On Thursday 21 June 2012, Mark wrote:
>> > >> Both issues are not something that obstruct normal KDE usage, but they
>> > >> do render some parts of KDE completely useless. I'm a bit u
On Thursday, June 21, 2012 16:13:32 Mark wrote:
> think we should make releases with random pieces cutted out, or they
> will never be complete" so we don't cut out pieces that don't work yet
> we also don't want to release pieces that don't work.
we don't WANT to, but we do.
this is the "perfec
On Thursday, June 21, 2012 16:58:28 Mark wrote:
> Ehhh, that's a very strange reasoning :p That way you could release a
> completely broken KDE SC (like KDE 4.0 was ;p) then developers will
this is not why the 4.0 release was made at the point it was, nor is it
comparable in scope as marco pointe
On Thursday 21 June 2012 16:56:51 Marco Martin wrote:
> On Thursday 21 June 2012, Mark wrote:
> > >> Both issues are not something that obstruct normal KDE usage, but they
> > >> do render some parts of KDE completely useless. I'm a bit unsure if i
> > >> should mark such bugs as release blockers.
On Thursday 21 June 2012, Mark wrote:
> > Nobody said we don't want to release pieces that don't work. We do
> > release pieces that don't work. Then those bugs are much more visible
> > and developers (hopefully) have more motivation to fix them. :)
> >
> > Just my 2c,
> > Jeremy
>
> Ehhh, tha
On Thu, Jun 21, 2012 at 4:44 PM, Jeremy Whiting wrote:
> On Thu, Jun 21, 2012 at 8:13 AM, Mark wrote:
>> On Thu, Jun 21, 2012 at 11:20 AM, Aaron J. Seigo wrote:
>>> On Wednesday, June 20, 2012 22:15:35 Mark wrote:
To me the definition of a regression is as follows:
A regression is an i
On Thursday 21 June 2012, Mark wrote:
> >> Both issues are not something that obstruct normal KDE usage, but they
> >> do render some parts of KDE completely useless. I'm a bit unsure if i
> >> should mark such bugs as release blockers.
> >
> > not when they are this minor, no.
>
> True and i com
On Thu, Jun 21, 2012 at 8:13 AM, Mark wrote:
> On Thu, Jun 21, 2012 at 11:20 AM, Aaron J. Seigo wrote:
>> On Wednesday, June 20, 2012 22:15:35 Mark wrote:
>>> To me the definition of a regression is as follows:
>>> A regression is an issue that wasn't in the previous release.
>>
>> that would des
On Thu, Jun 21, 2012 at 11:20 AM, Aaron J. Seigo wrote:
> On Wednesday, June 20, 2012 22:15:35 Mark wrote:
>> To me the definition of a regression is as follows:
>> A regression is an issue that wasn't in the previous release.
>
> that would describe all new bugs ;)
>
> a regression is something t
On Wednesday, June 20, 2012 22:15:35 Mark wrote:
> To me the definition of a regression is as follows:
> A regression is an issue that wasn't in the previous release.
that would describe all new bugs ;)
a regression is something that worked properly (for whatever that means in the
given situatio
On Wednesday 20 June 2012, Mark wrote:
> https://bugs.kde.org/show_bug.cgi?id=301854, that bug described the
> KGet Piechart applet as being broken. I tested that and verified that
> it indeed is completely broken and even renders outside it's applet
> space. So i marked that one as release blocker
On Wednesday 20 June 2012 22:15:35 Mark wrote:
> I would like to have some clarification on when something should be
> marked as a release blocker.
Take the word literally. A release blocker is a bug which makes the
release unusable. Think "it is better to not release KDE at all,
instead of rele
On Wed, Jun 20, 2012 at 10:50 PM, Martin Gräßlin wrote:
> On Wednesday 20 June 2012 22:15:35 Mark wrote:
>> Hi,
>>
>> Yesterday i was looking over quite a few plasma bugs and noticed a lot
>> of bug being filled at the new QML components.
>> I marked most of them as regressions since they looked l
On Wednesday 20 June 2012 22:15:35 Mark wrote:
> Hi,
>
> Yesterday i was looking over quite a few plasma bugs and noticed a lot
> of bug being filled at the new QML components.
> I marked most of them as regressions since they looked like regressions to
> me.
>
> To me the definition of a regress
Hi,
Yesterday i was looking over quite a few plasma bugs and noticed a lot
of bug being filled at the new QML components.
I marked most of them as regressions since they looked like regressions to me.
To me the definition of a regression is as follows:
A regression is an issue that wasn't in the
20 matches
Mail list logo
