3 ms·
>They keep old releases in their CI configuration and block PR’s from being merged if they don’t work on older release lines. Wait, people do that? If every PR
by wongarsu 9y ago
>They keep old releases in their CI configuration and block PR’s from being merged if they don’t work on older release lines.
Wait, people do that? If every PR lands on the next release and on the LTS release, how is the LTS branch different from the latest release? Isn't the point of LTS that it stays the same (except bugs) and isn't evolving?
I must be missing something obvious here.
- chrisseaton 9y agoI think they're talking about code bases that use the software with the LTS, not the code base of the software with LTS itself. They test against latest and LTS, and your PR needs to work on both.
- tdbgamer 9y agoSounds like the author picked a very specific case and assumed all LTS was that way. I've personally always understood LTS to be a feature freeze with only security patches being back ported. I've worked at places that did stuff like the author suggests without pinning versions, and it always just ends up with some unlucky person spending their weekend fixing a dumb bug cause by an upgrade. LTS is the reason we can all sleep soundly knowing our code won't spontaneously break, so I'm extremely grateful to the hard work everyone puts into it.