Bug reports posted as answers
asked 2015-06-14 01:53:55 +0300
Announcements (in this case, release notes) have started to gather bug reports and feature requests as answers.
Makes no sense. I think we should keep up with the familiar system, having one new question for each separate issue. What can we do to fix it, and prevent it from happening in the future? Or should it be acceptable, changing the way to sail here?
Added a bug-tag too, even that this bug is within us here :) Remove if incorrect
Related guideline: https://together.jolla.com/question/4389/together-howto-question-answer-and-comment/?answer=4393#post-id-4393
Update: This is happening again after 1.1.7. with already 30 answers there, could something be done?
sorry, deleted my post and renew as bug
evo3de ( 2015-07-15 17:55:10 +0300 )edit@simo how about upvoting that? https://together.jolla.com/question/104467/stickyimportantpinned-questions-functionality-on-tjc/
virgi26 ( 2015-08-25 14:57:42 +0300 )editIn my opinion thats a design problem of this system in the following ways. In this assumption I remove really wrong posted release anwsers that are just unrelated and should be bug posts.
- They create similar official public / non public release posts
- There are no attributes to put and filter a sailfish version the bug was found / is sticking to
- If you find distribution / very related problems to a released version its just too obvious to create a answer on this release than create an unrelated bug post
- We as users don't have a feel how jolla handles this system though we feel forced in creating sticky/related answers. Thats also a lack of response. I can speak from myself many times where I had to decide how and where I post stuff. Just now on a response to the non public release problems i felt forced to create an answer there.
CLR64 ( 2015-08-25 16:46:05 +0300 )editBingo!
pichlo ( 2015-10-25 00:59:33 +0300 )edit