From koffice-devel  Thu Sep 23 14:22:16 2010
From: Inge Wallin <inge () lysator ! liu ! se>
Date: Thu, 23 Sep 2010 14:22:16 +0000
To: koffice-devel
Subject: Re: Bugs against the Essen branch
Message-Id: <201009231622.16275.inge () lysator ! liu ! se>
X-MARC-Message: https://marc.info/?l=koffice-devel&m=128525177415203

On Thursday, September 23, 2010 15:46:03 zander@kde.org wrote:
> On Thursday 23. September 2010 14.09.10 Inge Wallin wrote:
> > > However, it is true that using bugzilla for bugs tested against that
> > > branch does not work well. Unless the bugs are correctly flaged as
> > > LATER or INFO.
> > 
> > So, is this the consensus then?  To indeed add the bugs and use status
> > LATER?  INFO seems strange to me since the info is supposed to be in the
> > bug already.
> 
> I don't like 'LATER' because the bug can very well be specific to the main
> branch only.
> 
> I think the testers should only reports bugs in bugzilla for bugs that can
> be reproduced in trunk. This information is important to decide if the fix
> should go on trunk and thus be scheduled for 2.3.0
> 
> As such the resolution of "NEEDMOREINFO" makes a lot of sense and thats why
> I asked for this.
> Notice, btw, that a bug that got the requested info quickly got scheduled
> properly.
> https://bugs.kde.org/show_bug.cgi?id=251562
> 
> So lets do the work and get the test done against trunk and make everyone
> happy :)

Hmmm

I think I can help the testers enough so that they can test both the branch 
and trunk.  The workflow will be such that they test the branch, and for the 
bugs that they actually find, they will test trunk too.

For bugs in that are in both, there is no problem.  Just report it against 
trunk, and when it is solved there it will be synced with the branch and 
everybody is happy.

The problem are those bugs that exist in branch but not in trunk.  I don't 
think NEEDMOREINFO is appropriate here because we already have all the 
information.  LATER would make more sense since it will move to something else 
later when the branch is discontinued.  Or it will get fixed, when it will be 
resolved anyway.

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel