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

List:       kde-core-devel
Subject:    Re: RFC: KDE Bugzilla Bugs Expiration
From:       Martin Klapetek <martin.klapetek () gmail ! com>
Date:       2015-07-31 9:31:02
Message-ID: CAPLgePrHvCSHZuZ-1KsK8Wy8TbFXtic-8EnnrhDb2+OLX5eB4g () mail ! gmail ! com
[Download RAW message or body]

On Fri, Jul 31, 2015 at 11:02 AM, Dominik Haumann <dhaumann@kde.org> wrote:

>
> Of course, some wishes and valid bugs would be automatically closed then,
> too.
> But this is probably not a big issue, since a wish that will never get
> implemented
> is useful neither for us as developers nor for the users at all.
>

I'd like to disagree with that^, in kde-telepathy we have many valid
bug reports/wishes which we would want to have/implement when
there will be that day when you have all the time you need. But we
just struggle to find the time.

They are useful for developers/maintainers because if a newcomer
shows up, you can just tell him "look at all the opened wishes,
pick one and work on it" (which we do regularly). It's also useful
when you have a free weekend and want to work on some of those
opened reports. Which you wouldn't be able if they would be all
closed.

They are also useful for users so they don't get reported again and
again.


> And if there are bug reports that from a developer's perspective should
> not be
> auto-closed, then we could attach a custom tag 'no-auto-close' or so to
> the bug.
> Then this script could ignore the tagged ones.
>

Yeah, this would be great.


> Comments? Strong objections? ;)
>

Personally I prefer the Dan's version with the EOL, but in general +1
to the idea.

Cheers
-- 
Martin Klapetek | KDE Developer

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 31, \
2015 at 11:02 AM, Dominik Haumann <span dir="ltr">&lt;<a \
href="mailto:dhaumann@kde.org" target="_blank">dhaumann@kde.org</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><br> Of course, some wishes and valid bugs would be \
automatically closed then, too.<br> But this is probably not a big issue, since a \
wish that will never get<br> implemented<br>
is useful neither for us as developers nor for the users at \
all.<br></blockquote><div><br></div><div>I&#39;d like to disagree with that^, in \
kde-telepathy we have many valid</div><div>bug reports/wishes which we would want to \
have/implement when</div><div>there will be that day when you have all the time you \
need. But we</div><div>just struggle to find the time.</div><div><br></div><div>They \
are useful for developers/maintainers because if a newcomer</div><div>shows up, you \
can just tell him &quot;look at all the opened wishes,</div><div>pick one and work on \
it&quot; (which we do regularly). It&#39;s also useful</div><div>when you have a free \
weekend and want to work on some of those</div><div>opened reports. Which you \
wouldn&#39;t be able if they would be \
all</div><div>closed.</div><div><br></div><div>They are also useful for users so they \
don&#39;t get reported again and</div><div>again.</div><div>  </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> And if there are bug reports that from a developer&#39;s \
perspective should not be<br> auto-closed, then we could attach a custom tag \
&#39;no-auto-close&#39; or so to the bug.<br> Then this script could ignore the \
tagged ones.<br></blockquote><div><br></div><div>Yeah, this would be \
great.</div><div>  </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> Comments? Strong objections? \
;)<br></blockquote><div><br></div><div>Personally I prefer the Dan&#39;s version with \
the EOL, but in general +1</div><div>to the \
idea.</div><div><br></div></div><div>Cheers</div>-- <br><div \
class="gmail_signature"><div><span style="color:rgb(102,102,102)">Martin Klapetek | \
KDE  Developer</span></div></div> </div></div>



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