3 ms·
OpenBSD, llvm, and go all have six month cadences.
by tedunangst 10y ago
OpenBSD, llvm, and go all have six month cadences.
- hyperpape 10y agoAnd do the same sorts of breaking changes get made, just distributed in smaller chunks through those six month releases?
- tedunangst 10y agoExactly.
- mixedCase 10y agoI don't know about OpenBSD and LLVM, but Go has made good on the Go 1 compatibility promise, with only a few minor changes being disputed as wether they break it or not. Go 2.0 will probably be a different story, assuming it ever comes out, but I have a hard time believing the devs will release anything that won't be fixable using the "go fix" tool.
- tbrock 10y agoAnd ubuntu and gnome and fedora and...
- hp 10y agoYep. it works well. https://wiki.gnome.org/ReleasePlanning/TimeBased https://wiki.gnome.org/ReleasePlanning/TimeBased
- usernam 10y agoI can only comment on the specific llvm case, but I cannot say "it works" without listing the fact that I have to keep ~5-6 versions of llvm around _exactly_ for that reason. You cannot compare an OS, or in general any product which is "complete by itself" (browsers), with a compiler which is then used to _make_ the end product. Your source depends on it, and as it grows it just becomes increasingly hard to keep up. Rolling releases are /also/ a tradeoff. I'm not particularly pleased with llvm in this case. I genuinely prefer semantic releases, and yes, even the python2->3 strategy in this context.