asked 2015-09-08 19:01:52 +0300
I'd like us to keep up with bug reporting only for officially released Sailfish OS versions (Early Access versions having the relevant numbered tag, public releases having what ever tags seem appropriate)
Any unreleased software IS NOT SUPPOSED TO BE FUNCTIONAL (otherwise it would be released, right?)
While writing this, the latest public release is 1.1.7.28, and there are no later Early Access versions released quite yet
answered 2015-09-09 01:55:01 +0300
I thoroughly disagree! Should this be about the thoroughly touted #unlike co-creation, doing it together, etc. ?
Isn't it enough that half of Sailfish OS is closed source so we have no idea about its progress/can't provide feedback/test/post fixes until it thrown over the wall in binary form ?
Are we now also supposed to ignore software once it finally shows up until it's final release ?
At which point it will be full of functionality/usability bugs due to normal users not having a chance to test it and provide feedback. Also ask any "software engineering 101" graduate how important it is to find and fix bugs early - and how difficult and expensive it is to fix issues that are found in final stages of development.
Also this more or less boils down to Askbot totally sucking as a bug tracking platform.
If this was a proper bugzilla you would just set the component version to something like "pre-release/alfa/beta/whatever" and be done with it - everyone would know you are reporting stuff in an unstable pre-release version and can easily filter for it or filter it out.
And you want as many people as possibly to test your software as early as possible!
For example there is no way in hell Fedora releases would be in any usable shape, even if the bunch of full time Fedora QA guys worked themselves to death, if it was not for the huge help of the Fedora community continuously testing the upcoming Fedora release all the way from branching to the final release.
Asked: 2015-09-08 19:01:52 +0300
Seen: 440 times
Last updated: Sep 09 '15
Don't agree. SFOS 2.0 is a major release with a shift in UX/UI and usability (and most importantly habit). Sailors should know what can cause problems even before it hits Early Access and maybe try to fix them. (even thought i don't expect them to react fast sadly :/)
Its kind of a special case.
ApB ( 2015-09-08 19:16:23 +0300 )edit@ApB I agree this is somewhat special case, but I guess that's why the Sailors have signed exactly their wanted amount of Sailors into the tablet developer program, already having their external testers in this group.
My guess is that most of these bug reports on unofficial software are just double posts with their current, more closed reporting channels, and these reports just fill up this portal and confuse new users on TJC
simo ( 2015-09-08 19:28:47 +0300 )editDo we have any real bug reports yet? I've seen quite a few complaints about UI changes, but changes aren't bugs. 1.1.9 must be quite stable if those are the only complaints. ;)
ossi1967 ( 2015-09-08 19:29:40 +0300 )edit@ossi1967 I calculated 5 bug-tagged so far, so this has just begun. Feature requests or UI change wishes are a whole different issue, those are not bug reports, and those are quite welcome too.
simo ( 2015-09-08 19:42:18 +0300 )edit@ossi1967
You can see it as a big usability testing session. While not "bugs" stuff like the one reported should be taken care of. I hope at least.
@simo
Don't know what the amount of sailors already having it -without hacks- consists but having a more diverse and with different views crowd can only be good. People see different things. Ie most coders have zero understanding of aesthetics usability UX etc. TBH i suspect the problems mentioned won't reach the design team which doesn't seem to frequent TJC a lot and seems to have a view of its own on the design aspects:/. Ie. most of the problems mentioned were reported after the first time SFOS2.0 was shown in public. Hope to be proven wrong on this and things get fixed before 2.0.
As for double reports TJC is not something that is added on the internal bugtracker automatically so i don't worry much about it.
ApB ( 2015-09-08 19:53:55 +0300 )edit