Feature / process improvement: Include security guidance in upgrade notice

[tripleee]

Description

When I get a pop-up that a new version of Brave is available and offering to download and upgrade, I spend time on reading through the release notes to assess whether this is an important update or not. Too often this is wasted effort (i.e. it is not, at least not obviously) which disrupts my work more than ideally I would like for it to.

Steps to Reproduce

1. Receive an upgrade notification pop-up
2. Click through to the README with the release notes for the new version
3. Check back with the update window to see how far back in the changelog to browse for security issues

Actual result:

More often than not, no really clear idea of whether to update or not; time spent on reviewing technical details which for the most part are not obvious to someone who is not involved in developing Brave

Expected result:

One of the following, in decreasing order of preference -- ideally, more than one of these:

1. A preference setting where I could simply check "don't bug me if it's not a security upgrade"
2. Right at the top of the upgrade notice, a clear, concise indication of any security issues, and (if relevant) further down. an itemized list of them with details about scope etc (e.g. "important if you have a Pizzazz Gizmo version 12 or earlier; but otherwise, nah")
3. In the changelog, include a similar summary of any security fixes in each version, with details in each item which provides changes which affect security.

Reproduces how often:

Every time I get an upgrade notice

Desktop Brave version:

Brave	1.19.86 Chromium: 88.0.4324.96 (Official Build) (x86_64)
Revision	68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}
OS	macOS Version 10.15.7 (Build 19H114)
JavaScript	V8 8.8.278.14
User Agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36
Command Line	/Applications/Brave Browser.app/Contents/MacOS/Brave Browser -psn_0_131104 --enable-dom-distiller --disable-domain-reliability --no-pings --extension-content-verification=enforce_strict --extensions-install-verification=enforce --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --sync-url=https://sync-v2.brave.com/v2 --lso-url=https://no-thanks.invalid --variations-server-url=https://variations.brave.com/seed --enable-features=AutoupgradeMixedContent,LegacyTLSEnforced,WebUIDarkMode,ReducedReferrerGranularity,PasswordImport,PrefetchPrivacyChanges --disable-features=AutofillEnableAccountWalletStorage,TextFragmentAnchor,VideoPlaybackQuality,TabHoverCards,PasswordCheck,NetworkTimeServiceQuerying,AutofillServerCommunication,IdleDetection,PrivacySettingsRedesign,NotificationTriggers,WebOTP,SignedExchangeSubresourcePrefetch,SafeBrowsingEnhancedProtection --flag-switches-begin --flag-switches-end --restore-last-session
Executable Path	/Applications/Brave Browser.app/Contents/MacOS/Brave Browser
Profile Path	/Users/XXX/Library/Application Support/BraveSoftware/Brave-Browser/Default

Android Device details:

• Install type (ARM, x86):
• Device type (Phone, Tablet, Phablet):
• Android version:

Version/Channel Information:

To the best of my awareness, this affects all channels, but I have not tried beta or nightly.

Other Additional Information:

As implied in the title, this probably requires process changes more than code changes.

Miscellaneous Information:

N/A