A bug’s life at Vivaldi
-
@guilimote I feel the same. My proposal would be include "uncoolness" into priority calculation.
-
If the bug stands for a long time, its "uncoolness" increases even if its initial priority was low.
-
Inconsistency is "uncool" even if the feature isn't used much.
because Vivaldi has to be "cool" if it wants to be chosen over the mainstream competitions.
-
-
I also just want to know if my bug was accepted as a bug, and/or what its' status is.
VB-55059 New Tab - blocking single key navigation - is still present in Vivaldi 2.9.1705.34 (Stable channel) (32-bit) Revision 44bd2b25227d4a11b8317dd46d602773bcdbe4df
-
@Christoph142 said in A bug’s life at Vivaldi:
Making the bug tracker publicly accessible is also a matter of missing JIRA licenses. It's simply not possible without paying a huge amount of money here.
Even exporting the list on the website with some kind of jira plugin?
Of course, internal discussions and undisclosed security issues should be kept private.
Sometimes I'd only like to scroll just a searchable list with VB name, category, description, status, info (if disclosed) and priority.
But I doubt will happen. -
@artpoetryfiction Hello there,
I seldom check bug status for users - there are a thread for that.
VB-55059 - confirmed -
It would be great to have a link somewhere on how we can punch in the Bug # of a bug we've filed and view status, add more info, etc. As it is right now, it's simply a black hole we throw information into.
-
@bc3tech There is a pinned topic in the Forum where you can inquire with moderators concerning the status of any bug.
See: https://forum.vivaldi.net/topic/27450/what-is-the-status-of-vb-already-reported-bug-issue/629
-
I've spent the last few hours trying to figure out where to start... The bug's life often should start as a comment / post I think. Or, even with effort, I fear casual users will often be wasting both their time and yours. We users are notorious for not knowing enough to even ask the right questions, let alone how to ask it. (I've been a non-coding CEO and CTO for over 30 years developing and licensing low-level code to major OEMs, and am overly cautious of sending engineers on well meaning fool's errands. Before taking anything I say seriously, there's typically an inquisition of sorts, or nothing should be done at all. 98% of the discussions I've brought up, get quickly killed at this stage, as they should be. But often, that 2% is where the gold is found, and serious problems have been avoided that would have affected million of users. But still, this is a very messy and costly process, since most of the time, I really don't know what I'm asking for, or trying to report.)
I have a specific problem right now, but seriously can't determine if it is a bug, feature request, or a dumb end-user problem that I should have quickly found the answer to by myself, but didn't. The other problem in submitting anything via forum or bug report is understanding enough of the user requirement / environment. The most important issue is, "What's the value proposition if the bug is confirmed or fixed??" For instance, I use Vivaldi in ways that few users do, or should do, and as a result, this causes problems 98% of other users, will never see. Still, my stress testing will likely expose flaws that will impact everyone to some extent.
I'll make a separate new post that will hopefully not waste other's time, but improve Vivaldi and user experience. My problem is best described as a startup issue, or better defined as a startup crash. I simply can't get to, change, or even close any screen, setting, menu, window, tab, etc. I also cannot open a different profile to even use the Vivaldi browser to research my problem--thus, I'm using Opera for now. I have the ability to easily destroy a profile, and "fix" my problem. But, I'm trying to preserve my last session, which has a lot of work already open in those windows, that would take me a week to recreate. My choice without help and/or hours of work, are to totally abandon using Vivaldi until I find an acceptable fix, or cutting off my arm and destroying my profile and losing all that work from the open windows.
Given these parameters, should I create a bug report? I doubt it. At least not yet. Guidance for users on which forum to use would be very helpful to them, while saving your devs considerable time and frustration. Let me know what you think, (with an alert and/or an email added.)
-
This is down to simple semantics,I don't know myself how many bugs exist within vivaldi but i would hazard a guess they outnumber the manpower at vivaldi technologies.
In a nutshell vivaldi does not have the equal manpower to google or mozilla etc.So the more that users report a single bug then it could become a priority.
This has drawbacks as time marches on because if the bugs start getting bigger in number and remain unfixed then the browser will become broken over time. -
@Priest72 There are in the tens of thousands of bugs, and about 20 devs who might address them.
-
@Ayespy said in A bug’s life at Vivaldi:
tens of thousands of bugs
Yeah, but there was only ever one feature.
Was.
-
@Steffie May she RIP.
-
@Ayespy I've flagged you for a Mod's attention, for going OT. Honestly!
:face_with_stuck-out_tongue_winking_eye:
-
This post is deleted! -