3 ms·
Why not run 1-2 releases behind and test/qualify a later release? A commenter below gave a good example of a company that would need to run a bleeding edge ker
by Cyph0n 4y ago
Why not run 1-2 releases behind and test/qualify a later release?
A commenter below gave a good example of a company that would need to run a bleeding edge kernel (Red Hat). The vast majority of companies would never need to do that though.
- fiedzia 4y ago> Why not run 1-2 releases behind and test/qualify a later release? This may work for most people, but not all. It's easier to get things fixed while developers still work on something, than weeks/months later. Also if you have not most-popular hardware/software configuration, testing done by others isn't necessarily sufficient for you.
- sph 4y agoMaybe your company needs that super duper new feature that's on master. Or you're Google scale and that 0.5% improvement in IO throughput would save you millions a year. You wouldn't want to wait until it hits the stable branch if possible.