View Single Post
Old 04-26-2013, 06:43 AM   #565
PeterT
Grand Sorcerer
PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.
 
Posts: 13,567
Karma: 79436716
Join Date: Nov 2007
Location: Toronto
Device: Libra H2O, Libra Colour
Quote:
Originally Posted by Anak View Post
Can a new prefix be added to post? Prefix: Touch Glo Mini Aura?
Now it only possible to select one device. A little "problematic" for soms threads as future firmware features requests and firware bugs: same bugs and same feature request for different devices (now Touch and Glo).
My opinion: firmware releases are for all devices: Touch, Glo, Mini and Aura. So bugs and feature requests apply to all devices. Except when noted or a feature (e.g. front light) is limited to some devices. But still should be posted in the same thread.

Second, can a list of reported bugs/issues/requests added to the first or second post of the threads? It's quite complicated to find out if a bug already has been reported. As the threads are usually long and also contain remarks, work arounds etc.

E.g.
Known bugs
Open
* (some) dictonaries not functioning: wrong format (#posting number) (# firmware release)
* annotations/bookmark issues (#posting number) (# firmware release)

Closed/Solved (by Kobo, no user work arounds)
* issue (#posting number (# firmware release)

Where:
#posting number: first posting reporting a bug/issue in current or previous thread.
# firmware release: bug/issue first appeared in firmware release number x.x.x)


You'll get the idea. Better suggestions are welcome.
It also becomes much easier to track Kobo's efforts to solve known bugs.
Feel free to take on the challenge.......
PeterT is offline   Reply With Quote