locked
.Net Core support policy - which version to use RRS feed

  • Question

  • User324835512 posted

    Hi all,

    This may be the wrong place for this - please let me know.

    I'm looking at the official support policy for .Net Core : https://dotnet.microsoft.com/platform/support/policy/dotnet-core

    I see that 2.1 is in 'long-term support (LTS)', while 2.2 is 'Current' - with support ending on Dec 23, 2019.

    I also see that 3.0 is about to be released in 'Current', and 3.1 in a couple of months with 'LTS'.

    I've recently started work on a new project that's scheduled to go to production in November.  So I'm wondering what version to target.

    2.1:

    Pro: LTS

    Con: Doesn't have the newest features

    2.2:

    Pro: Current version

    Con: Short support lifetime

    3.0:

    Pro: latest and greatest

    Con: Not yet released, but should be on Monday.

             Short support lifetime

    3.1:

    Pro: latest an greatest

           LTS

    Con: Not yet released

             Released right around the time I'm going to prod

    I don't want to release a brand-new app that has support for less than a month after it goes live; I also don't want to take the risk of a framework upgrade right at release date.

    So what's the official guidance on what to do here?  What happens if I release something on 2.2 - how long do I have to upgrade? 

    I have an aggressive deadline, so I don't have much time for framework issues; so I'm a little nervous about 3.0.  But I won't have time at the end of my release cycle to upgrade.

    Thanks,

    Phil

    Wednesday, September 18, 2019 5:58 PM

All replies

  • User-474980206 posted

    you pick an update cadence you can support. (which is more important, stability or features).

    an LTS release is supported for 3 years after its release (so 2.1 has almost 2 years left),  it planned to have 2 years between LTS releases. As LTS releases are 2 years apart, this gives you 1 year to upgrade after the new release is out. 

    if you pick a current release, then after the next release, you have 3 months to update to the next release.

    if three months is not enough time to do an upgrade, then pick the LTS cycle. Once you pick a current cycle, you are stuck with the short upgrade cycle until the next LTS release.

    so you can pick 2.1 LTS, or use 3.0 and be required to update to 3.1 by feb 2020. Only you can answer this question.

    note: there will not be a 4.* series, to avoid confusion with the current asp.net 4.*. after the 3.1 LTS release, core is jumping to 5.* 

    Wednesday, September 18, 2019 11:59 PM