4 ms·
Unfortunately in some industries continuous delivery is literally illegal. Anyway there's a real issue with their current schedules. Let's say you're developing
by kcb 4y ago
Unfortunately in some industries continuous delivery is literally illegal. Anyway there's a real issue with their current schedules. Let's say you're developing software some time in the middle of next year. There's effectively no LTS release available at all.
- TillE 4y agoWe're not talking about "continuous delivery", this is just having a plan to ship updates every two years, on a well defined schedule. If you can't manage that organizationally, there are deeper problems. It's not really Microsoft's job to work around your awkward requirements. Everything is open source, you can ship patches for .NET 6 yourself if you really want to.
- phillipcarter 4y agoThe answer is to fix your processes, not demand Microsoft accommodate them. The lifecycles are already plenty long.
- to11mtm 4y agoMy issue is the cadences are difficult to work with. Microsoft's general-ish LTS for .NET is 2 years. We also only seem to get a new release every 2 years. It's hard to handle breaking changes between two versions quickly.
- phillipcarter 4y agoLTS for .NET is 3 years, not two. There's a new LTS every 2 years, so you get a full year to move from LTS -> LTS if you need to. What kind of breaking changes have been hard to handle?
- simooooo 4y agoNone so far
- kcb 4y agoAny way you look at it 3 years is pretty low for industry standard LTS lifecycles. Besides the .NET Framework comparison Java LTS is 5-8 years.
- phillipcarter 4y agoNode (used at least as much as .NET and Java in enterprise) has a 3 year LTS cycle, so I don't know if it's really low for an industry standard.
- BeefWellington 4y agoNode (used at least as much as .NET and Java in enterprise) has a 3 year LTS cycle I'm gonna need a citation on that. From what I've seen, what enterprises have done any node adoption have fled it like rats fleeing a sinking ship because of all the problems it's had over the past half decade. To the point that shops I've worked with are moving back to Java.
- pjmlp 4y agoIt is quite clear on node's documentation. https://github.com/nodejs/release#release-schedule https://github.com/nodejs/release#release-schedule
- blargpls 4y agoPretty sure they are asking for a citation on the usage and not on the LTS schedule.
- phillipcarter 4y agoI've seen the opposite.