Changelog or Release Notes Anyone?



  • As it was brought up several times by now, the last time being this (IIRC) month ago, am I just too dense to find a change-log or release notes on given versions, the most recent one or at all?

    Why are change-logs/release-notes kept spread over the forum, posted on the blog – being made available (if at all) on a variety of places instead a static one? Why is it made such hard to keep oneself informed over changes?

    I know one goes with the flow by artificially reduce every information given to a stylish presented white space while declaring your customer under-age these days, but can we for the sake of information get a single, un·chan·ging place where one can find a given change log aka release-notes for a given release please?!

    In this sense

    Smartcom


  • Moderator

    Snapshots:
    Changelogs for can be found at Snapshots blog https://vivaldi.com/blog/snapshots/.
    It is advised to read the blog before updating a Snapshot.

    Stables:
    Unfortunately not so easy to find.
    But it is useful to check https://vivaldi.com/blog/teamblog/ for Stable informations.

    Perhaps the devs could make a link to a Stable changelog on the Download page. I asked them today.



  • @gwen-dragon
    C'mon, why there ain't any release-notes in the first place on a static place – as they were published in the beginning? Weren't change-logs of initial versions just published on https://update.vivaldi.com/update/X.x/relnotes/Major.minor.build.html?

    Pretty much every serious developer does that. As a matter of facts it's quite numbingly to crawl the blog, reddit or the general web for a given change-log if you want to install it. I may note here that's somewhat strange to be in the need for asking about release-notes prior to install a given software-package in the first place … It's just absurd though.

    In this sense

    Smartcom


  • Moderator

    @smartcom5 Yes, can be found.
    For for the Stables f.ex 1.13.1008.40 at
    https://update.vivaldi.com/update/1.0/relnotes/1.13.1008.40.html

    I will tell someone to contact you.



  • @Gwen-Dragon
    What links and from where (!?) does link towards this very site?
    I've spend about an hour to find any change-notes on the 1.13 stable one and gave up eventually.

    See, all I want to know is, if the bug is fixed which broke BBCode-forms since a while now as Vivaldi keeps spamming BBCode all over the form completely un-replicable and for whatever reasons – sometimes it's working, most of the times it's not. Same as the utmost Forum-braking bug which caused to return to the previous site upon using ⌫ within the very BB-form.

    You know, staying that questionable while displaying this level of secretiveness in terms of release-notes ain't getting you any new numbers of sophisticated users. It's a bloody change-log after all, right?

    In this sense

    Smartcom



  • @gwen-dragon said in Change log or release-notes anyone?:

    […]
    Stables:
    Unfortunately not so easy to find.
    But it is useful to check https://vivaldi.com/blog/teamblog/ for Stable informations.

    To expect your supposed (new) users to do so is somewhat … I don't know, really.
    It's just a joke and we both know that.

    Perhaps the devs could make a link to a Stable changelog on the Download page. I asked them today.

    A direct link to the very release-notes under https://update.vivaldi.com/update/X.x/relnotes/Major.minor.build.html please, yes. That's the least one have to do if you claim to bear any kind of respectability on your own while claiming you're standing within the footprints of former Opera 12.x users or so-called Power-users in general …

    In this sense

    Smartcom


  • Moderator

    @smartcom5 said in Change log or release-notes anyone?:

    all I want to know is, if the bug is fixed which broke BBCode-forms

    I do not have bugs with editing forms and Backspace.
    But please report the bug.


    How to do a bug report for Vivaldi

    Report each bug separately at https://vivaldi.com/bugreport/
    Describe the issue as precise as you can.
    Add some information about extensions you use.
    Add information about the operating system and version you use.
    Add some information which security tools you use.
    If you have problems with video or audio give us information about your installed codecs and graphics
    card/GPU.
    Add a exact link to the page where the issue comes up and can be tested.
    After reporting the issue, you will receive a confirmation mail from the bugtracker.
    In a reply to this mail you can add more information and files (like screenshots or testcases) as
    attachments and it will be added automatically to bug report.

    If you have questions about the bug please ask in forum first and do not forget to post the VB-XXXXX
    bug number (you can find it in confirmation mail).

    Thanks in advance for helping us to make Vivaldi better!



  • Community Manager

    @smartcom5 Hi, you raise a fair point. We'll look into this.



  • In the meantime you can use this copy-pasted change log collection
    https://forum.vivaldi.net/topic/23608/snapshot-changelogs-starting-with-the-first-1-12-snapshot



  • @olgaa Thank you, really apppreciated! ☺

    In this sense

    Smartcom


 

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