It looks like the rash of bugs reported after the public Alpha was made available has stopped. That is a really good sign. :cool:
txcas
-
-
- Bug Zapper
- Posts: 202
MultiformeIngegno
-
-
- Posts: 1,337
Wasn't this "thoughts" material? :P
Nao
- Dadman with a boy
-
-
- Posts: 16,079
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 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
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.
Nao
- Dadman with a boy
-
-
- Posts: 16,079
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.
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
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).
People can log a ticket (or you can create them as you see them, or volunteers can).
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
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.
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
error: brain is not installed or configured
Farjo
- "a valuable asset to the community"
-
-
- Posts: 492
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.
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.