Upgrading to 16.04 can render the system permanently broken

flocculant at gmx.co.uk flocculant at gmx.co.uk
Tue Apr 26 16:45:35 UTC 2016


On 26/04/16 17:01, Brian Murray wrote:
> On Tue, Apr 26, 2016 at 03:50:09PM +0100, flocculant at gmx.co.uk wrote:
>> On 26/04/16 15:36, Alberto Salvia Novella wrote:
>>> ...
>> No.
>>
>> This is not about bug importance at all.
>>
>> That is a different issue.
>>
>> What I am saying is that adding HundredPaperCuts - then that never changing
>> - mucks up our bug tracking.
> Could you elaborate on how having a task for a project that isn't Ubuntu
> affects your ability to track the bug?
>
> Thanks!
> --
> Brian Murray
Not sure exactly - but our tracker isn't able to differentiate between 
packages/projects on a bug afaik.

Consequently - bugs we know are fixed end up showing other statuses.

The same would apply if say for instance a thunar bug ended up with 
maybe gvfs affecting - our tracker wouldn't differentiate - that's not a 
problem - they're both real issues at that point.

Our 'problem' with the 100 paper cuts issue - is that while they may 
eventually get marked as fixed - it's not when our tracker 'should' be 
showing it - but some indeterminate point in the future.

That project 'might' point issues out to others who 'might' do something 
towards fixing a bug - but experience shows us that xubuntu bugs are 
almost always fixed 'in-house' or at Xfce , consequently it makes life 
hard for us - and we're all working towards the same thing hopefully - a 
strong *buntu community.





More information about the Ubuntu-quality mailing list