Brave 隐私浏览器 bate版 nightly版 release版有什么区别？

讲真 我懒得叨叨了

直接看官方的界面 https://github.com/brave/brave-browser/wiki/Brave-Release-Schedule

这个浏览器真的很好 隐私保护6的一逼 速度是Chrome的好几倍  嘎嘎唰唰的飞

更新更是不用说 三个版本 分别是对应周几更新 release正式版甚至都列出表来了 已经排到了1.72.x的计划 时间到2024年12月！

我只能跪拜和佩服！

伙计们看下面的原文吧 很好懂！  官方这个地址 应该是随时更新的  https://github.com/brave/brave-browser/wiki/Brave-Release-Schedule

Overview

Currently published version numbers can be seen at https://brave-browser-downloads.s3.brave.com/

• Major Release frequency: ~3 weeks
• Minor Chromium/Security releases: Every Tuesday (within ~24hrs after released) as per Chromium schedule. (however, these are tentative and subject to change)
• Chemspill/Hotfix frequency: As needed
• Every major release is tied to a fuzzy Chromium release date.

Older Brave Release Schedules are available in the Brave Release Schedules Archive.

Information about channel differences available in the Release Channel Descriptions.

Current channel information:

Note: These versions represent which channel our CI builds things on. It may not reflect exactly the version on release channel for example. This would happen if for example Release above said 0.58.x and it was in RC but on our website we still offered 0.57.x.

Current build schedule:

The following is our automated schedule for creating and uploading builds to our Sparkle (macOS), Omaha (Windows) servers and our Linux repositories.

Release channel dates:

Note: As announced via https://security.googleblog.com/2023/08/an-update-on-chrome-security-updates.html, we'll be getting minor chromium bumps every Tuesday. These releases will sometime also include P1 & P2 issues that are deemed important enough to get out ASAP rather than waiting for a major release. For example, HackerOne reports or other issues that are affecting users in a major way.

• All dates are approximate and are subject to change.
• Maintenance releases are tentative and subject to change.
• Migration Date is also the cutoff date to add strings that need to be translated for the release.
• Updates will be released as requested only.

Number of days between each release on Release channel

Beta channel migration dates:

• CI does builds for Beta channel happen twice a week.
• Updates are released as there are builds as long as tests pass.

Nightly channel migration dates:

• Nightly builds will be made from master for this channel.
• This means that within a day of any change you can start testing it.
• Developers work off of master.
• We keep master stable, when it is not, we backout what broke it.
• If something fails tests, that thing should be backed out.
• brave/brave-browser's package.json specifies brave-core branch to be master.

Mobile platforms

Android rollout process

When 1) approved in the Google Play Store and 2) QA has signed off on the release, we'll release in a staged rollout. Before moving to the next stage, crash reports are checked by release team and evaluated.

Assuming we have the release ready in the morning, the schedule will typically look like this:

iOS rollout process

When 1) approved in iOS App Store and 2) QA has signed off on the release, we'll begin the automated rollout. This takes place over 7 days to people who have automatic updates enabled. Users can visit the App Store page for Brave at any time and get the latest one

If something goes wrong, the release can be paused.

How to do branch migrations:

• Visit https://ci.brave.com/job/branch-migrations/
• Queue the job
• Verify results

For folks that want to see more of "how the sausage is made" (link restricted to Brave employees), you can view the Jenkins job details here: https://github.com/brave/devops/blob/master/jenkins/jobs/browser/branch-migrations.yml