-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some dialog still says "Chromium" #167
Comments
Also in Settings, if you search for Chrome, you will get some results. (excluding the Chrome Web Store) |
Supermium 121 is in the process of building and needs to be tested on every platform of significance (and some features that were removed by upstream between 119 and 121 need to be put back in as well). Once this is done, a branding script will be run and the objective is to get every instance of Chromium (and apparently Chrome, even though Chromium shouldn't even reference Chrome as it's a separate product) replaced with Supermium in all languages. This will not be reflected in the source code because there are frequent changes to the strings that will cause git conflicts. |
@win32ss can you increase release frequency? We don't mind beta builds as long as they are marked as unstable, and we can help you with testing. Thank you for your work. |
Supermium only rebases on the stable upstream version at the end of the version's development cycle. As a result, features and bugfixes are incrementally produced on the base of the previously-released version. Then any breaking changes associated with the new version are corrected. So any intermediate releases would contain new features but otherwise have no differences in terms of the upstream content. It is possible that a paid "early access model" could be implemented for the intermediate releases, which would also cover the standard 32 bit XP build. |
I like that idea, at least you'd get supported by all the time you are putting in. And the public builds would support winxp, or? |
Can you fix it in next release?
The text was updated successfully, but these errors were encountered: