Revision history [back]
 | 1 | initial version | posted 2015-06-14 01:53:55 +0200 |
Bug reports posted as answers
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
| | 2 | No.2 Revision |
Bug reports posted as answers
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
| | 3 | No.3 Revision |
Bug reports posted as answers
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.24, so bringing this one up for a while.
| | 4 | No.4 Revision |
Bug reports posted as answers
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.24, so bringing this one up for a while. while.
Update2: 18 answers there now, anyone care to pick the correct one https://together.jolla.com/question/98953/release-notes-117-bjorntrasket/
| | 5 | No.5 Revision |
Bug reports posted as answers
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.24, so bringing this one up for a while.
Update2: 18 answers there now, anyone care to pick the correct one https://together.jolla.com/question/98953/release-notes-117-bjorntrasket/
Update3: Release notes keeps popping up, now with 22 answers, could something be done? Not difficult to solve anyway
| | 6 | No.6 Revision |
Bug reports posted as answers
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.24, so bringing this one up for a while.
Update2: 18 answers there now, anyone care to pick the correct one https://together.jolla.com/question/98953/release-notes-117-bjorntrasket/
Update3: Release notes keeps popping up, now with 22 answers, could something be done? Not difficult to solve anyway
Update4: 28...
| | 7 | No.7 Revision |
Bug reports posted as answers
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.24, so bringing this one up for a while.
Update2: 18 1.1.7. with already 30 answers there now, anyone care to pick the correct one https://together.jolla.com/question/98953/release-notes-117-bjorntrasket/
Update3: Release notes keeps popping up, now with 22 answers, there, could something be done? Not difficult to solve anyway
Update4: 28...done?