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

List:       koffice-devel
Subject:    Re: Bugs against the Essen branch
From:       "LukasT.dev () gmail ! com" <lukast ! dev () gmail ! com>
Date:       2010-09-23 9:03:46
Message-ID: 201009231103.46455.LukasT.dev () gmail ! com
[Download RAW message or body]

I'm Krita developer, let me share you my non-involved view.

> Recently the Nokia testers have started to report bugs against the Essen
> branch.  This is part of the Nokia effort to open up the development
> process and put it more into the open, something I think we should be
> grateful for.

Cool move from Nokia! Why they started to test Essen? Is there any particular 
feature they are dependent on when testing that is not in trunk?
 
> However, this hasn't been well received everywhere.  Thomas has moved the
> resolution of these bugs to WAIT [1] and asking that the testing be done
> against trunk instead.  He writes:
> 
> "Please test against the main branch and not an unstable
> feature branch thats not supported by the KOffice core team.
> Feel free to reopen if the bug exists in the main branch. "

Who is the KOffice _core_ team? :) Am I in the club? =)
 
> So, I can see these alternatives:
> 
> 1. Nokia is allowed to report bugs against the branch.
> 2. Nokia is not allowed to report bugs and will move back to the internal
> Maemo.org bugzilla.
> In case 1, there will be a few bugs that cannot be reproduced in trunk. 
> That is a cost, but in my mind not very high.  In return we will get a lot
> of bugs reported that would otherwise go unnoticed by us.
> In case 2, we will save some work (won't have to check the bugs against
> trunk) but we miss out on a lot of bugs. It will also mean a setback to
> the opening up process.

I think that if they report bugs against features that are not in trunk, 
let them allow to fill the bugs, but set the bug to WAIT. If the bug is in 
trunk, ask them to test also the trunk and then the bug can be set to NEW.
This is valuable for community I think. Otherwise it adds half work for 
community. Question is why they do just the half of the work?

Also I think as developer the new bugs from some feature branch are seen as 
noise if there are quite many of them. You focus on stabilization and you try 
to triage the bugs when they are reported and if you do not follow Essen, then 
you can't reproduce and you waste your time. 

Have fun!
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]