Hi
on the Sailfish Support Page:
"
Bug Tracking Tool
We are in a phase of rapid development, so a formal bug tracking tool
is not the best solution yet. Nevertheless, we would like to hear your
feedback via the mailing list.
"
This always struck me as a little bit weak / weird. I would have
thought that a small team working hard on a fast developing project
needs a bug tracking tool just as much as any other, possibly even
more so. But I agree, it does not need to be formal, but there should
be something to ensure that issues don't get lost.
This list is great for discussing stuff we find. As we are all
learning, many of our problems may not actually be caused by bugs,
rather by mistakes we are making. But if after a bit of discussion it
is decided that the behaviour is down to a bug, then it would be great
to be able to park the issue somewhere knowing it won't get lost.
Chris
Zitat von "Thomas B. Rücker" <tho...@ruecker.fi>:
On 08/07/2013 10:17 AM, Putze Sven wrote:
Hi there,
is there a bugtracker for reported issues or new issues anywhere
around (Sailfish OS / SDK / Installer)? Or is everything handled
via this list here so far?
For the first alpha release there was a significant collection of known
issues listed on the page. Bugs are mostly reported here and on IRC
(although here is better for documentation purposes).
Issues that can be clearly identified to have originated in Mer or Nemo
are tracked here:
- https://bugs.merproject.org/
- https://bugs.nemomobile.org/
I'm not entirely sure how Jolla owned bugs are prioritized. The one I
reported with one of my first mails to the list in February (and got
ack'd by Jolla) is still there.
Cheers
Thomas
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
