Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-01-28 10:01:05 +0200

Concerning bug and xx.xx.xx.xx version tags.

Currently we have: - bug x 628 - possible-bug x 14 - 1.0.1.10 x 1 - 1.0.1.12 x 1 - 1.0.2.5 x 27

I am sure it would be useful for the developers to know which version a bug is found in, but asking people reporting the bug to add the proper version tag might be a bit tedious.

Instead, I propose to use sailfish-xx.xx.xx.xx-bug, for example sailfish-1.0.2.5-bug. This way, if people report a bug, they will be implicitly asked to check their Sailfish OS version. Naturally, the bug tag would continue to exist as it might be used for apps. But this approach might at least help the developers with some reports.

Concerning retagging (if we agree on the above approach), we can base it on the date of report in combination with the release date.

Not sure what to do about the possible-bug tag though.

Concerning bug and xx.xx.xx.xx version tags.

Currently we have: - bug x 628 - possible-bug x 14 - 1.0.1.10 x 1 - 1.0.1.12 x 1 - 1.0.2.5 x 27

I am sure it would be useful for the developers to know which version a bug is found in, but asking people reporting the bug to add the proper version tag might be a bit tedious.

Instead, I propose to use sailfish-xx.xx.xx.xx-bug, for example sailfish-1.0.2.5-bug. This way, if people report a bug, they will be implicitly asked to check their Sailfish OS version. Naturally, the bug tag would continue to exist as it might be used for apps. But this approach might at least help the developers with some reports.

Concerning retagging (if we agree on the above approach), we can base it on the date of report in combination with the release date.

Not sure what to do about the possible-bug tag though.

Concerning bug and xx.xx.xx.xx version tags.

Currently we have: have:

  • bug x 628 628
  • possible-bug x 14 14
  • 1.0.1.10 x 1 1
  • 1.0.1.12 x 1 1
  • 1.0.2.5 x 27

I am sure it would be useful for the developers to know which version a bug is found in, but asking people reporting the bug to add the proper version tag might be a bit tedious.

Instead, I propose to use sailfish-xx.xx.xx.xx-bug, for example sailfish-1.0.2.5-bug. This way, if people report a bug, they will be implicitly asked to check their Sailfish OS version. Naturally, the bug tag would continue to exist as it might be used for apps. But this approach might at least help the developers with some reports.

Concerning retagging (if we agree on the above approach), we can base it on the date of report in combination with the release date.

Not sure what to do about the possible-bug tag though.