Page 1 of 1

Suggestion for Basilisk Download Page

Posted: 2021-09-02, 01:13
by ggbce
Hi,

I really appreciate Basilisk UXP Web Browser. To improve deployment and keep a high security level in a large enterprise, we need to always get updated our computers (and deployment sources)... Then I need to take time to browse each applications that we use and verify if we actually use the latest version, ensure that no security problem exist, etc.

Then, my suggestion is:

Please, in your download page (https://www.basilisk-browser.org/download.shtml), add the version number near of the download link, and add a fast link to a release history note like we can found from many other application. And, in this release history if we could see improvment, security (CVE) fix if exist, know problems, etc.

Regards !

Re: Suggestion for Basilisk Download Page

Posted: 2021-09-02, 11:48
by Falna
An alternative would be to monitor the release notes page using the Update Alert add-on.

Re: Suggestion for Basilisk Download Page

Posted: 2021-09-02, 12:20
by ggbce
Add-on need to be a end-user of Basilisk Web Browser. In my case we have hundred users use it where IT staff need to monitor/update many computer with tools like PDQ Deploy, SCCM, BatchPatch. Their job is to retrieve updated versions of each application, not only Basilisk. Then, it's not a "good solution" in this case.

Regards

Re: Suggestion for Basilisk Download Page

Posted: 2021-09-02, 13:03
by Moonchild
Release notes are linked from the Basilisk home page. Just have your IT staff put a watch on that page and you will have the version update, and all release information that is relevant.

Re: Suggestion for Basilisk Download Page

Posted: 2021-09-02, 13:33
by ggbce
Hi,

I juste give a suggestion because it's not optimized to search on every pages to find necessary information. Basically, just telling what we download (Version number on click to Download) could be be efficient.

Re: Suggestion for Basilisk Download Page

Posted: 2021-09-02, 14:07
by Moonchild
But that isn't efficient for us because then we'll have to update multiple pages for each release -- the version is listed on the release notes page.