On 07/04/2010 01:11 AM, Tim McNamara wrote:
Hi devs,
500+ unclosed bugs causes problems. I feel intimidated overwhelmed by
this number. I also find it difficult to find material sift through bug
reports, to find areas where I can help (although, at the moment, I'm
quite content with
On 07/04/2010 05:15 PM, Bernie Innocenti wrote:
El Sun, 04-07-2010 a las 02:29 +0100, Gary Martin escribió:
Also, I don't know if I have the permission to change resolution
status when something hasn't been touched for 12+ months. If I were
to change status on likely candidates, would this
Excerpts from Tomeu Vizoso's message of Mon Jul 05 10:47:44 + 2010:
[...] or possibly something like Unfortunately, we have higher priority
areas to work on right now.
Never close bugs because nobody has time to fix them. Rather use the
priority field to indicate the maintainer isn't
El Sun, 04-07-2010 a las 02:29 +0100, Gary Martin escribió:
Also, I don't know if I have the permission to change resolution
status when something hasn't been touched for 12+ months. If I were
to change status on likely candidates, would this anger the other
developers?
I know it's
Hi devs,
500+ unclosed bugs causes problems. I feel intimidated overwhelmed by this
number. I also find it difficult to find material sift through bug reports,
to find areas where I can help (although, at the moment, I'm quite content
with sugar-love level problems). However, 500+ bugs isn't
Excerpts from Tim McNamara's message of Sat Jul 03 23:11:42 + 2010:
Some have been identified as upstream problems, but their resolution status
remains open.
That's because they still affect users. Some might need Sugar changes
once they have been handled upstream.
The current status fields
On 4 Jul 2010, at 00:11, Tim McNamara paperl...@timmcnamara.co.nz wrote:
Hi devs,
500+ unclosed bugs causes problems. I feel intimidated overwhelmed by this
number. I also find it difficult to find material sift through bug reports,
to find areas where I can help (although, at the
7 matches
Mail list logo
