Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2011-11

Silly bugtracker question

10 messages · 8 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Bart

Hi,

Here's a silly question.

In the Lazarus bugtracker we have > 1600 issues marked as resolved. A little under half of them are > 1 year old.

Shouldn't most of these issues be closed (preferrably not by hand), or doesn't it matter anyhow?

Bart

Reply by email

Alexander Shishkin
to Bart

30.11.2011 1:50, Bart ?????:

Show quoted text 19 lines
Hi, Here's a silly question. In the Lazarus bugtracker we have> 1600 issues marked as resolved. A little under half of them are> 1 year old. Shouldn't most of these issues be closed (preferrably not by hand), or doesn't it matter anyhow? Bart -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

IMHO It`s better to think about resolving open issues rather than closing resolved ones.

Reply by email

Bart
to Alexander Shishkin
Alexander Shishkin wrote
IMHO It`s better to think about resolving open issues rather than closing resolved ones.

I do that too, and occasionally I actually fix some of them.

I stated it was a silly question to begin with ;-)

However, it looks untidy to me.
(And obviously I have too much time on my hand right now)

Bart

Reply by email

Martin
to Bart: Here's a silly question. In the Lazarus bugtracker we have > 1600 issues marked as…
Bart wrote 10 lines
Hi, Here's a silly question. In the Lazarus bugtracker we have> 1600 issues marked as resolved. A little under half of them are> 1 year old. Shouldn't most of these issues be closed (preferrably not by hand), or doesn't it matter anyhow?

I don't know if there is any rule in place, what closed vs resolved should mean.

If an issue is fixed then it gets set to resolved, this allows the original reporter to add further notes or reopen the issue. So issues should definitely be in resolved state first and for some time.

Currently sometimes closing is left to the reporter, who sometimes is no longer around...

IMHO a rule that mores sense is to close them, when a release is made that contains the fix, that way people who do not follow trunk, will see resolved issues if they search for something.

Reply by email

Felipe Monteiro de Carvalho
to Martin
Martin wrote
I don't know if there is any rule in place, what closed vs resolved should mean.

There is, closed means that the reporter has verified that the fix works. In other bug trackers this state is called "Verified"

There is also a second rule that after 3 months we can give up on verification feedback and close the issue anyway. But I always thought that this was done automatically.

Felipe Monteiro de Carvalho

Reply by email

Vincent Snijders
to Felipe Monteiro de Carvalho

2011/11/30 Felipe Monteiro de Carvalho :

Show quoted text 10 lines
On Wed, Nov 30, 2011 at 12:56 AM, Martin wrote: > I don't know if there is any rule in place, what closed vs resolved should > mean. There is, closed means that the reporter has verified that the fix works. In other bug trackers this state is called "Verified" There is also a second rule that after 3 months we can give up on verification feedback and close the issue anyway. But I always thought that this was done automatically.

It was done by Marc in the past.

I would close 'automatically' until there was a release with the bug fix.

Vincent

Reply by email

Marc Weustink
to Vincent Snijders
Vincent Snijders wrote 13 lines
2011/11/30 Felipe Monteiro de Carvalho: > On Wed, Nov 30, 2011 at 12:56 AM, Martin wrote: >> I don't know if there is any rule in place, what closed vs resolved should >> mean. > > There is, closed means that the reporter has verified that the fix > works. In other bug trackers this state is called "Verified" > > There is also a second rule that after 3 months we can give up on > verification feedback and close the issue anyway. But I always thought > that this was done automatically. It was done by Marc in the past.

Yep, that automatic process was me (and I totally forgot about that ;)

Marc

Show quoted text 10 lines
I would close 'automatically' until there was a release with the bug fix. Vincent -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Reimar Grabowski
to Marco van de Voort
Show quoted text 5 lines
On Wed, Nov 30, 2011 at 12:55:38PM +0100, Marc Weustink wrote: > Yep, that automatic process was me (and I totally forgot about that ;) Aargh, that reminds me I still have to close the 2.4.4 issues :-)

Could someone with administrative rights please issue the following command?

sudo service marc restart && sudo service marco restart

Sorry guys, couldn't resist. :)

R.

Reply by email

Marco van de Voort
to Reimar Grabowski
Reimar Grabowski wrote 8 lines
> > Yep, that automatic process was me (and I totally forgot about that ;) > > Aargh, that reminds me I still have to close the 2.4.4 issues :-) Could someone with administrative rights please issue the following command? sudo service marc restart && sudo service marco restart Sorry guys, couldn't resist. :)

Actually, 2.4.4 was the first time I did this, Jonas used to do it till then.

Reply by email