4 ms·
Another important thing is Chrome's rapid release process works under the assumption that most issues that crop up will be fixed quickly in a later version, rat
by newhouseb 11y ago
Another important thing is Chrome's rapid release process works under the assumption that most issues that crop up will be fixed quickly in a later version, rather than be back-ported. Which is to say that there are no Ubuntu-esque LTS versions of Chrome, so whatever random bugs happen to exist in the version of Chrome that each vendor forks will likely be there for a long long time, making this fiasco that much worse.
- deleted 11y ago[deleted]
- digi_owl 11y agoSeems like Google is trying to apply web development methodology to software...
- CydeWeys 11y agoWhat does this have to do with web development in particular? Regardless of the kind of software involved, if YOU fork, it's YOUR responsibility to merge upstream patches and fixes over time. If the various vendor-branded Chromia aren't doing it, then it's entirely on them. Upstream Chromium is open source, and the code for all of those fixes and patches is available in the open.
- digi_owl 11y agoDon't bother with a LTE/patch-only branch, just "iterate iterate iterate" as the just user coming down the net connection will get your latest anyways...
- serge2k 11y agoMaintaining a fork as complex as Chromium is probably more work than these companies are willing/able to do.
- cloudwalking 11y agoThen they shouldn't fork it.