Pretty quiet here

txcas

  • Bug Zapper
  • Posts: 202
Pretty quiet here
« on February 12th, 2014, 07:54 PM »
It looks like the rash of bugs reported after the public Alpha was made available has stopped.  That is a really good sign.  :cool:

MultiformeIngegno

  • Posts: 1,337
Re: Pretty quiet here
« Reply #1, on February 12th, 2014, 09:45 PM »
Wasn't this "thoughts" material? :P

Nao

  • Dadman with a boy
  • Posts: 16,062
Re: Pretty quiet here
« Reply #2, on February 12th, 2014, 11:50 PM »
Well, there are still a couple new bugs being reported per day, but yes, I'm trying to go through the log of existing bugs I hadn't looked into yet... There are a lot. I took tonight's bug report from Farjo's recap post in the 'Preparing for an official package' topic.

I need to appoint someone or some people to maintain an official "Nao, this needs attention!" topic for me... :P And strike out things that I've worked on, etc.
Heck, there are also issues on the github repo (from Xarcell)... :-/
Plus, all of the issues that weren't closed but were actually incorrect bug reports.

Xarcell

  • Posts: 30
Re: Pretty quiet here
« Reply #3, on February 13th, 2014, 02:53 AM »
Quote from Nao on February 12th, 2014, 11:50 PM
Well, there are still a couple new bugs being reported per day, but yes, I'm trying to go through the log of existing bugs I hadn't looked into yet... There are a lot. I took tonight's bug report from Farjo's recap post in the 'Preparing for an official package' topic.

I need to appoint someone or some people to maintain an official "Nao, this needs attention!" topic for me... :P And strike out things that I've worked on, etc.
Heck, there are also issues on the github repo (from Xarcell)... :-/
Plus, all of the issues that weren't closed but were actually incorrect bug reports.
Where would you rather I report them?

Nao

  • Dadman with a boy
  • Posts: 16,062
Re: Pretty quiet here
« Reply #4, on February 13th, 2014, 03:04 PM »
Well, there's a "bug reports" board here.
I don't mind having reports over at GH, though. It's just that I'd like to have all open reports (including GH's) gathered in a single post/topic, so I can go fishing for bug fixing more easily.

Bunstonious

  • Espada
  • Posts: 204
Re: Pretty quiet here
« Reply #5, on February 14th, 2014, 02:17 PM »
Perhaps a "helpdesk" piece of software would suit.

People can log a ticket (or you can create them as you see them, or volunteers can).
Quote from Random Guy
Not putting miles on your Ferrari is like not having sex with your Girlfriend so she'll be more desirable to her next Boyfriend

Pandos

  • Living on the edge of Wedge
  • Posts: 635
Re: Pretty quiet here
« Reply #6, on February 14th, 2014, 03:12 PM »
IMHO the Bug-Board is absolutely sufficient.

The only thing that matters if to mark a topic as solved and move it to archived fixes when done.
# dpkg-reconfigure brain
error: brain is not installed or configured

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: Pretty quiet here
« Reply #7, on February 15th, 2014, 02:16 PM »
Quote from Nao on February 12th, 2014, 11:50 PM
Well, there are still a couple new bugs being reported per day, but yes, I'm trying to go through the log of existing bugs I hadn't looked into yet... There are a lot. I took tonight's bug report from Farjo's recap post in the 'Preparing for an official package' topic.

I need to appoint someone or some people to maintain an official "Nao, this needs attention!" topic for me... :P And strike out things that I've worked on, etc.
Heck, there are also issues on the github repo (from Xarcell)... :-/
Plus, all of the issues that weren't closed but were actually incorrect bug reports.
I can copy and update my post to a new topic in the bug board if it's useful.

A proper issue-tracking package would be ideal with its statuses (reported, confirmed, revision available, fixed etc), but there isn't one for Wedge (and wedgedesk isn't going to be fixed) and an external one would not work. There are not too many issues at any one time so a list should suffice.

The bug board / marking solved is also useful in principle but 1. people do not mark topics as solved and 2. coders are too keen to mark solved when they have made an untested or unconfirmed fix. This means that the list of topics is an inaccurate indicator of issues outstanding.