A bug’s life at Vivaldi


  • - Ambassador -

    @christoph142 said in A bug’s life at Vivaldi:

    sending status updates to the reporter's mail address is very much possible. We have been discussing this internally a few times already and I'm going to continue being an advocate for this.

    This is something that I have been wondering about for quite some time now. If a user reports a bug or thinks they have found a bug it makes perfect sense to keep the bug reporter in the loop. Simply assign the users email to the VB number and voila the reporter is instantly kept up to date. And, please keep advocating for this to happen.

    Now I reported VB-35804 Sadly sometimes no news is not good news.


  • Moderator

    @para-noid I also agree that it would be great for users to get an update on their bug's status, even if it's just to notify you that the bug has been confirmed, and especially important (for everyone concerned) if you file a bug for a serious issue and it gets closed with a status of "cannot reproduce".

    Also, if you file a bug and would like to provide some additional information to the developers, you can always reply to your bug confirmation email and include those details.

    That said, the bug tracker is not used for discussion so you really, truly are not missing out on anything exciting between submitting a bug and seeing the fix appear in a Snapshot. You may also find this surprising but most of the interesting discussions about issues concerning Vivaldi actually goes on in these forums. It's the nucleus and nexus for the entire Vivaldi community and a critical resource for everyone. If you're running into an issue, it important to discuss it here, and to confirm issues that other users report as well.



  • One more argument, why clients like to know about the state of "their" bugs:
    I am interested in these states:

    • Not reproducible
      It may indicate that the problem is either with my machine or I should work on my way to explain problems
    • Duplicate
      I can forget about this, somebody (probably) looks out for it
    • By design
      ok, not a bug

  • Moderator

    @para-noid: Your issue got closed as "Cannot reproduce". But honestly, it's more of an "Invalid". If you experience an issue, please ALWAYS test without any extension and only submit a report if it still happens. (This coming from an extension developer!)


  • - Ambassador -

    @christoph142 said in A bug’s life at Vivaldi:

    @para-noid: Your issue got closed as "Cannot reproduce". But honestly, it's more of an "Invalid". If you experience an issue, please ALWAYS test without any extension and only submit a report if it still happens. (This coming from an extension developer!)

    Thanks. Will do.


  • - Ambassador -

    @christoph142 said in A bug’s life at Vivaldi:

    @para-noid: Your issue got closed as "Cannot reproduce". But honestly, it's more of an "Invalid". If you experience an issue, please ALWAYS test without any extension and only submit a report if it still happens. (This coming from an extension developer!)

    Disabled all extensions. Same issue. For what it's worth Firefox has more extensions and wunderground.com loads fine.


  • Moderator

    @para-noid said in A bug’s life at Vivaldi:

    @christoph142 said in A bug’s life at Vivaldi:

    @para-noid: Your issue got closed as "Cannot reproduce". But honestly, it's more of an "Invalid". If you experience an issue, please ALWAYS test without any extension and only submit a report if it still happens. (This coming from an extension developer!)

    Disabled all extensions. Same issue. For what it's worth Firefox has more extensions and wunderground.com loads fine.

    Hi, seems to me to work correctly, what's the matter with you?
    0_1515787049156_78d05303-11b0-4797-a683-797267c13eb5.png

    PS: Tried with a clean profile?



  • @olgaa I think that the main issue with the current bug process is that even if no bug is ignored "in theory", it seems to be the case "in practice".

    Let me explain my self:
    You explain that Vivaldi's team apply on every relevant issue a priority from 1 to 5, then letting each developer choosing which ticket to work on.
    If I am a Vivaldi developer, the logical way to do that would be: "I pick an un-assigned issue, dealing with a component on which I am qualified to work on, with the highest priority."

    The problem with this strategy is that there will always be high priority issues / change requests. As a consequence, lots of "low priority issues" will never be treated, or won't be closed until they are switched to an "un-relevant" status because too old. (I assume it must be done sometimes?)

    The consequences:

    • You may miss unexpectedly important stuff. A low priority issue can sometimes hide something more complex / more interesting / with higher priority (because ticket analysis was incorrect, or because after analysis, the root cause let you think about other potential or existing issues not yet reported).
    • The "low priority" status may be relevant because not impacting most of the users... Nevertheless it can still be critical for a small amount of users. In this case, theses users can think they are forgotten.
    • Even when it is a low priority issue with no other impact for everybody: having no communication, no acknowledgment, no planning, no info for weeks / months / years is a motivation killer, even for users with the highest commitment. Whatever the final priority of the issue, some users spend a very long time to isolate and reproduce them, to analyze the best they can and report meaningful tickets on the tracker.

    A proposal (but there may be other ways of solving these kind of problems):

    • Some tickets still need to remain immediately treated, like crashes or showstoppers for upcoming release
    • The other tickets may be distributed using other criteria than only priority. For example,
      • In a 5 days week, spend 4 days to work on high priority tickets
      • In a 5 days week, always spend 1 day (or half a day) to work ONLY on low priority tickets, at least those which can be quickly solved

    If I take may own pet bugs for example, there are a few of them which can clearly be solved very quickly (or they look like it)... but are here for more than a year without any change / info. As a user which tries to help you, it is very demotivating when you have a the feeling that the right guy would fix it in 30min if it was looked at in details 😞

    Anyway, this long post is mainly the expression of my frustration because I have high hopes about Vivaldi's project. So don't get it wrong, if I have high expectations, it is because Vivaldi is already a great project!
    What you have acomplished with such a small team in comparison to the web giants is incredible. Keep it up! 🙂



  • @guilimote I feel the same. My proposal would be include "uncoolness" into priority calculation.

    1. If the bug stands for a long time, its "uncoolness" increases even if its initial priority was low.

    2. 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.


  • Moderator

    @artpoetryfiction Hello there,

    I seldom check bug status for users - there are a thread for that.
    VB-55059 - confirmed


  • Moderator



  • 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.


  • Moderator

    @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.


  • Moderator

    @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.


  • Moderator

    @Steffie May she RIP.


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.