Bug/feature tracking mechanism?

CoolDragon · 06-03-2010, 02:05 PM

I am wondering what is required to setup a bug/feature tracking system/mechanism for the IREX devices. This forum is a good place to post anything, but not very good for tracking bugs/feature requirements. Anybody knows how to setup a new project on launchpad?

Mackx · 06-04-2010, 03:58 AM

Maybe MobileRead can supply some kind of service for this? I guess that owners of other devices would also want a 'known issue' list.
This mechanism will need some moderation to avoid too many duplicates (and thus keep the overview) and some severity (how worse is the problem) and a priority (how fast, would we users, want to have this fixed). A 'work-around' section would also be usefull, specially for the DR where the source code for the firmware is released and thus users can make their own patches.

pauli · 06-04-2010, 04:38 AM

the developers hub: https://dev.mobileread.com/trac/hub/
has this kind of function... it uses tickets people can file a bug or a feature request
people must register for the dev hub and it has moderation included

but I am not sure this would be allowed by MR, because this project wouldn't develop something, no open source code is created. If it's ok with them, I'd happy to moderate it.

Mackx · 06-04-2010, 09:01 AM

Quote:

Originally Posted by pauli

but I am not sure this would be allowed by MR, because this project wouldn't develop something, no open source code is created. If it's ok with them, I'd happy to moderate it.

It would be a good place to archive/collect patched firmware code! (to fix/work-around the issues in the official firmware).

Shaggy · 06-07-2010, 05:53 PM

Ideally, you would probably want a bug tracker that was run by iRex, not a third party site.

Mackx · 06-08-2010, 06:51 AM

Quote:

Originally Posted by Shaggy

Ideally, you would probably want a bug tracker that was run by iRex, not a third party site.

Well, that depends, I think that we as users would want to determine the priority, from a user point of view. Also as a user we would want to determine if a problem is a problem (e.g. no continues zoom on 800, from a user point of view could be considered a bug, from irex it seems to be a marketing choice). Having it hosted by iRex could mean that you lose some freedom.

Shaggy · 06-08-2010, 11:45 AM

Quote:

Originally Posted by Mackx

Well, that depends, I think that we as users would want to determine the priority, from a user point of view. Also as a user we would want to determine if a problem is a problem (e.g. no continues zoom on 800, from a user point of view could be considered a bug, from irex it seems to be a marketing choice). Having it hosted by iRex could mean that you lose some freedom.

Maybe, but ultimately you'd need participation from them on the tracker in order to get the bugs fixed. Or are we talking about a bug tracker for 3rd party apps?

Mackx · 06-08-2010, 12:18 PM

Quote:

Originally Posted by Shaggy

Maybe, but ultimately you'd need participation from them on the tracker in order to get the bugs fixed.

Yes, but I assume that the problems reported here, or via their service desk, already end-up in their tracker. By having a 'user bug-list' you can better indicate the priority of a bug, as experienced by real-users, to iRex and get them high on their list for the next (bugfix-)release.

Shaggy · 06-08-2010, 01:05 PM

Quote:

Originally Posted by Mackx

Yes, but I assume that the problems reported here, or via their service desk, already end-up in their tracker. By having a 'user bug-list' you can better indicate the priority of a bug, as experienced by real-users, to iRex and get them high on their list for the next (bugfix-)release.

Yeah, that's kind of what I had in mind as well. I just thought synchronization between a user tracker and the iRex tracker would be easier if it was the same tracker.

06-03-2010, 02:05 PM	#1
CoolDragon Addict Posts: 244 Karma: 124 Join Date: Feb 2010 Device: none	Bug/feature tracking mechanism? I am wondering what is required to setup a bug/feature tracking system/mechanism for the IREX devices. This forum is a good place to post anything, but not very good for tracking bugs/feature requirements. Anybody knows how to setup a new project on launchpad?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Import Date: Bug or Feature?	DobraGolonka	Calibre	19	08-24-2010 12:47 PM
Bug or Feature?	capidamonte	Calibre	5	07-27-2010 04:06 PM
Epubreader opens always in current tab - bug or feature?	cklammer	EPUBReader	3	12-13-2009 09:59 AM
thermal experiences - bug or feature?	ThR	iRex	5	09-09-2009 03:13 AM

06-04-2010, 03:58 AM	#2
Mackx Guru Posts: 999 Karma: 19985 Join Date: Dec 2008 Location: Netherlands Device: iRex DR1000S	Maybe MobileRead can supply some kind of service for this? I guess that owners of other devices would also want a 'known issue' list. This mechanism will need some moderation to avoid too many duplicates (and thus keep the overview) and some severity (how worse is the problem) and a priority (how fast, would we users, want to have this fixed). A 'work-around' section would also be usefull, specially for the DR where the source code for the firmware is released and thus users can make their own patches.

06-04-2010, 04:38 AM	#3
pauli Groupie Posts: 185 Karma: 119824 Join Date: Feb 2008 Device: iLiad, DR1000S, HTC Hero, DR800SG	the developers hub: https://dev.mobileread.com/trac/hub/ has this kind of function... it uses tickets people can file a bug or a feature request people must register for the dev hub and it has moderation included but I am not sure this would be allowed by MR, because this project wouldn't develop something, no open source code is created. If it's ok with them, I'd happy to moderate it.

06-07-2010, 05:53 PM	#5
Shaggy Wizard Posts: 4,293 Karma: 529619 Join Date: May 2007 Device: iRex iLiad, DR800SG	Ideally, you would probably want a bug tracker that was run by iRex, not a third party site.