You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The Chromium builds that FFUpdate downloads are so-called "snapshots". These are not stable builds, but they are created automatically several times an hour from the current source code. Nobody tests them, they are really pure development builds that should not be used in everyday life, as the risk of data loss or serious problems is very high. The "stable" Chromium builds usually have to be compiled yourself, unfortunately the Chromium team does not provide anything other than the snapshots. The Cromite project provides stable Chromium builds, they are referred to there as "Vanilla Chromium" and are in the assets for the Cromite releases, although they still contain slight changes and are only created after the normal Cromite build, which is because they are mainly created to test which problems are with Cromite and which changes cause problems with other patches. But they may also be good enough to be integrated into FFUpdater, preferably with a warning. Describe the solution you'd like
A clear and concise description of what you want to happen.
Add a warning that the Chromium builds that FFUpdater pulls can be very unstable, as with other beta apps like Firefox Beta. Maybe the warning should sound a bit more "dangerous" though, even normal beta versions of Firefox or other browsers are at least tested, not even that is the case with Chromium snapshots.
Is your feature request related to a problem? Please describe.
The Chromium builds that FFUpdate downloads are so-called "snapshots". These are not stable builds, but they are created automatically several times an hour from the current source code. Nobody tests them, they are really pure development builds that should not be used in everyday life, as the risk of data loss or serious problems is very high. The "stable" Chromium builds usually have to be compiled yourself, unfortunately the Chromium team does not provide anything other than the snapshots. The Cromite project provides stable Chromium builds, they are referred to there as "Vanilla Chromium" and are in the assets for the Cromite releases, although they still contain slight changes and are only created after the normal Cromite build, which is because they are mainly created to test which problems are with Cromite and which changes cause problems with other patches. But they may also be good enough to be integrated into FFUpdater, preferably with a warning.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Additional context
More information about Chromium Snapshots and the different Release channels: https://www.chromium.org/getting-involved/dev-channel/#how-do-i-choose-which-channel-to-use
Example for the stable Chromium file based on the latest release: https://github.com/uazo/cromite/releases/tag/v130.0.6723.67-4ea5bf603a6c721f35dce9edcab04ff4f03ecbaa you see the VanillaChromium files in the assets.
The text was updated successfully, but these errors were encountered: