JoomlaCode Issue tracker report 28 March 2014

[brian teeman]

Folks if we want to successfully start using the new JIssue tracker we need to rapidly cleanup the existing joomlacode issue tracker. I spent just a few hours today and updated the status on about 100 issues which were either moved to Pending as we have a Pull Request and people can test or were closed for various reasons.

As of today 28 March 2014

Open 144

Confirmed 200

Pending 299

RTC 20

TOTAL Open Status 699

We all have a tendency to look at new issues and work on issues that interest us. As a result 177 of these have not been updated in any form in 2014 (much higher if we include status updates) and have no Pull Request. If we collectively review these old issues I strongly suspect many of them have already been resolved (we all know joomlacode is lousy for searching so duplicate reports happen a lot), they are feature requests or simply requests for support.

I would even go far as far and suggest that any issue (109) with no update in over 6 months and without any Pull Request is automatically closed without wasting any time investigating it. A new can always be created. 

I strongly believe that of the 700 open issues we have no more than 250 real live issues 

[Hannes Papenberg]

I can only second Brian here. Especially the Confirmed ones need a
complete review, because lots of those are simply old and have been
fixed in one form or another.

Hannes

> --
> You received this message because you are subscribed to the Google
> Groups "Joomla! CMS Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to joomla-dev-cm...@googlegroups.com
> <mailto:joomla-dev-cm...@googlegroups.com>.
> To post to this group, send email to joomla-...@googlegroups.com
> <mailto:joomla-...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/joomla-dev-cms.
> For more options, visit https://groups.google.com/d/optout.

[Lara Petersen]

What about issues that are Pending (or moved from RTC to Pending), because a decision has to be made first? (for example #33286)

Is there a separate @ for stats we can use, to identify these issues?

Regards, 

Lara

Op zaterdag 29 maart 2014 00:36:35 UTC+1 schreef brian teeman:

[brian teeman]

Do they even need a review if they are old?

Because the search is so poor, and that's why were dumping it, I bet the vast majority are either already fixed or not important. Heck if they were then they wouldn't have been left untouched for so long.

Let's just close them now. If they are still real issues then people can always create new issues which being new have a much higher chance of being looked at.

Its time to be brutal!!!

[brian teeman]

I should add that if we add all the issues that have just had a status change or requrst for more info in the last 6 months but no real activity then we would be automatically closing another 100-150.

When you can see the wood from the trees it is easier to build a house

[Dmitry Rekun]

Brian, 

may be we could have such stats on the main page of the JTracker, for exampe in the footer? Of course that could happen when we will totally move to the JTracker and have all statuses in place there.

Dmitry

суббота, 29 марта 2014 г., 11:40:38 UTC+2 пользователь brian teeman написал:

[brian teeman]

It would be interesting to have the stats on the new tracker. But not much more than that.

[Hannes Papenberg]

What is keeping us from closing the old tracker for new items right now?

We still have to go through all existing tracker items on JC, but it
would be very helpfull if we could prevent any new items from being
created which would have to then be merged over to the new tracker.
Especially considering that we apparently don't require a JC tracker
item for new PRs right now.

Hannes

[Valentin Despa]

There is a lot of work that needs to be done, very similar to handling paperwork (moving things from tray A to tray B, putting a stamp) with very little results.

I need an average from 10 - 15 minutes per bug (confirming, testing or researching). This makes gives me an efficiency of maximum 10 bugs per hour. Hope you guys are faster than me! 

After we bury the old tracker maybe we will get some automated scripts to manage the status of the bug.

Something like:

- opened longer than 3 months

- latest comment older than 3 months

- little or no votes on the "Experienced this issue / Importance of issue"

=> silently close the issue till somebody replies (regardless of the status).

It's shitty for the person who reported it in the first place, but I see no other option.

I think if we manage to clean the issues, on the new tracker we might have a chance in keeping things simpler, focusing on solving issues and not on "paperwork". I've noticed that the longer an issue stays in the tracker, the fewer chances it will ever get fixed.

Valentin Despa

[Nick Savov]

Hi guys,

Thanks for working on that! Feel free to close any that are over 6 months
without an update. However, please do so with a snippet asking for an
update and letting people know why it's closed and how to reopen it.

Thanks again!

Kind regards,
Nick

> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to joomla-dev-cm...@googlegroups.com.
> To post to this group, send an email to joomla-...@googlegroups.com.

[brian teeman]

If the PLT and/or the Bug Squad maintainers will write that "snippet" I'm happy to spend the time applying it

[Nick Savov]

Cheers Brian, I'll get it written today and send it over.

>> > email to joomla-dev-cm...@googlegroups.com <javascript:>.

>> > To post to this group, send an email to

>> joomla-...@googlegroups.com<javascript:>.

[Nick Savov]

How does this sound? (Feel free to edit it to your liking)


Hi,

Thanks for working on this bug report!

Due to the time lapse since its last activity, the issue is potentially
resolved via another ticket and/or is no longer up-to-date with the latest
Joomla version. We're marking this ticket as closed, however at your
earliest convenience please give us an update so that the ticket can be
reopened if there's still an issue.

Thanks again for your help!

Sincerely,
...

[Leo Lammerink]

Nick,
Think that still leaves too much open. I would change the late part and
have the message as follows:

Thanks for working on this bug report!

Due to the time lapse since its last activity, the issue is potentially resolved via another ticket and/or is no longer up-to-date with the latest Joomla version. We're marking this ticket as closed, however feel free to open a new issue on our new tracker when you are under the impression that the issue still exists

Thanks again for your help!

Regards,
....

------------------
This reduces the "non-confirmed issues and other old stuff" and you can with that remove all old stuff but keep the opportunity for those who want to reopen a new tracker item..... Seems like more efficient maybe?

Thoughts?

Leo Lammerink
MD GWS-Desk.com

[Nick Savov]

Good suggestion, Leo. That works for me. It just needs a link to the new
tracker, since most people don't know what or where it is.

Kind regards,
Nick

[Leo Lammerink]

aware of that. Please add at will?
Cheers
Leo

[brian teeman]

Thanks for submitting and/or working on this bug report! 

Due to the long period of time since there has been any activity on the report, the issue has potentially been resolved via another ticket and/or is no longer up-to-date with the latest Joomla version. We're marking this ticket as closed, however feel free to open a new issue on our new tracker (http://issues.joomla.org) if you find  that the issue still exists with the current release of Joomla

[Nick Savov]

Looks good to me.

Cheers,
Nick

[Andrew Eddie]

Brian I'm taking a "bug hunt" session next week at the Brisbane JUG. What's the best thing I can be focusing on to help in this regard?

Thanks in advance.

Regards,

Andrew Eddie

[Hannes Papenberg]

I'd say that depends on what you and the JUG are interested in doing. If
you wanna do administrative work and if we want to stick with "close
everything older than 6 months", you could do that. If you wanna do
simple testing, you could go through the confirmed issues and either
reconfirm or close them. For serious testing, test the open PRs. ;-)
These tasks are the most urgent ones in my regard. I also tend to sort
by date ascending, to finally handle all those really old issues.

Hannes

> --
> You received this message because you are subscribed to the Google
> Groups "Joomla! CMS Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to joomla-dev-cm...@googlegroups.com

> <mailto:joomla-dev-cm...@googlegroups.com>.
> To post to this group, send email to joomla-...@googlegroups.com
> <mailto:joomla-...@googlegroups.com>.

[Andrew Eddie]

Ok, thanks. That's helpful. Where's the best place to refer people to
for up-to-date JBS procedures?

Regards,
Andrew Eddie

> You received this message because you are subscribed to a topic in the Google Groups "Joomla! CMS Development" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/joomla-dev-cms/t8wnBKzDAdw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to joomla-dev-cm...@googlegroups.com.
> To post to this group, send an email to joomla-...@googlegroups.com.

[brian teeman]

http://community.joomla.org/blogs/leadership/1813-we-need-your-help.html
Thats as good as any for HOW to test

>> <mailto:joomla-dev-cms+unsub...@googlegroups.com>.

[George Wilson]

The best thing is to try and test existing PR's in my solution. In my experience at the bug hunt's everyone codes solutions for confirmed problems but very few people actually test the existing PR's. And that's pretty much the most useful thing we can be doing - especially with 3.3 upcoming

Kind Regards,

George