The Spring Framework differentiates between actively supported versions, versions that are "not actively supported anymore", and versions that reached end-of-life (EOL). Indeed for the 5.0 & 5.1 line, there have been no more releases after the announced "no--more-support" date of December 2020.
So what's the difference between "no active support" and EOL? Will e.g. libraries be updated if there's a CVE?
Similarly, Spring Boot differentiates between EOL & end of OSS support. While it claims that e.g. the 2.2.x line has OSS support until October 2020 and reaches EOL July 2021, releases have been made until January 2021, but none after that.
So what exactly happens in the time after OSS support has ended and EOL is reached? What can one expect here?
Both uses the same concept. EOL means that you will not get any patches, help or anything in any form for those versions.
End of OSS support and "no--more-support" means that you would get security patches as well as "severe" bugs up to EOL date.
In my experience, there has been some security updates for the versions between "end-of-support" and EOL but I do not recall a patch for a bug in any.
So, what it means is that, EOL versions in production should definitively be upgraded but you can wait a but for end-of-support. But, I would always recommend upgrading at a faster pace than that. If I do not need/want the newer features, I usually wait for x.x.1 but upgrade at that point - Spring Boot might be a little longer if you have dependencies that take some time to be compatible. i.e. Tanzu Application Service is still not updated for Spring Boot 2.5 - easiest way to check it out is through start.spring.io
As far as I understand the main difference is.
OSS = Open source support - eg. you get support through github issues until that date.
EOL = End of life - even if you bought a subscription for commercial support through VMware (which is the company behind spring) for spring, you wont get any more support for this version after that date. So no security fixes or patches wont be delivered anymore.
So EOL is more critically and even important for business which bought commercial support for longer use of that particular version, whereas OSS end is relevant for most of the users.
You already linked the relevant parts - Spring Boot Support Policy
Commercial support is also available from VMware which offers an extended support period.
in contrast to
Spring Boot releases are marked as "end of life" when they are no longer supported or released in any form.
To answer your question for what you can expect after end of OSS. You most likekly still get security issues fixed but no support (except maybe commercial support) when you run into issues.
Related
I am using OpenTelemetry for a long time for my tracing-related solutions, but now I want to also try logging and metrics support. As I am able to see both are in development and not released yet, so are there any plans to release for a stable version?
It's not 100% clear what release is in question but generally there are specification releases and then there are releases in specific implementations of the specification (.NET, Go, Java, ...). In another dimension we have parts of the specification (e.g. API and SDK), they have their own releases and timelines.
You can see the general status on GitHub and - more succinctly - on the OpenTelemetry web here.
As of now (Feb 14 2022), metrics are actually quite stable:
I am new to ODL. I'm using Northbound Networks ZodiacFX switches to learn with.
All the tutorials I read are written on the basis that l2switch is up and working. Without this working I have to manually build all flow table entries to allow basic switch connectivity.
1) What versions of ODL have this feature available
2) Why was proactive l2 switch programming feature removed from ODL?
Thank you.
l2switch was removed in Fluorine, so any version before that (Oxygen would be
the most recent) should have l2switch.
It was removed because the project no longer had an active community. It would
be welcome to revive if there were contributors willing to do the work.
I am currently working on USD 1.0 which is of-course a very old version of USD.
We are trying to move to the newest version of USD in my organization, which i believe is USD 4.0
I have tried searching the web but other than the MSDN article i have been able to gather much detail on this version.
I am trying to figure out my possibilities in trying to adapt to this newer version. In light of it, i have a few questions listed below,
Has Microsoft released only the preview/trial version of USD 4.0 yet? Or is it made available for general public which means we can access and start developing in our production environment?
Is the new version of USD, a web based version? I have heard that
this version is not the desktop application like it was before.
Will it be safe to migrate from USD 1.0 to USD 4.0?
Microsoft has also introduced Unified Client Interface, what is it?
Is it available only with USD 4.0?
Features comparison with USD 1.0?
If Microsoft have released the preview version only, then when will
they release the stable version? (any tentative date)?
Also, if they have released the preview version just then obviously they might change it in future. Therefore, it will not be wise enough to migrate to it if it is just a preview version.
Looking forward to your answers. Any sort of videos, articles, documentations, press releases, your personal opinions are welcome.
Thanks
Most 'manual' based MSDN information has been moved to Microsoft Docs: https://learn.microsoft.com
USD 4.x is still a desktop application that loads MSD components. You can upgrade to a more recent version 3.2 quite easily:
You can upgrade a Unified Service Desk 1.x or Unified Service Desk 2.0 sample application package to Unified Service Desk 3.2 by importing the Upgrade sample application package. The upgrade will not affect the configuration data associated with the existing solution.
Follow the steps here:
https://learn.microsoft.com/en-us/dynamics365/customer-engagement/unified-service-desk/admin/upgrade-unified-service-desk-solution?view=dynamics-usd-3
From there on forward it is much more easy to compare 3.x with 4.x and answer all your remaining questions.
Neil Parkhurst also has a ton of information.
https://neilparkhurst.com/2016/06/20/usd-the-book/
It is important to me to know whcih version of software should I use?
Last or Stable?
For example:
Laravel 5.5 (Stable) or Laravel 5.6 (Last)
cPanel 68.0.19 (Stable) or cPanel 68.1.1 (Last)
There are two options with Laravel:
Long Term Support
For those not familiar with long-term support, these are special versions that are feature locked at the date of release. They do not get any new features but keep getting bug fixes and security updates throughout the maintenance window.
For LTS releases, such as Laravel 5.5, bug fixes are provided for 2 years and security fixes are provided for 3 years. These releases provide the longest window of support and maintenance. For general releases, bug fixes are provided for 6 months and security fixes are provided for 1 year.
Version 5.1 was Laravel’s first LTS release.
LTS versions are popular with companies looking to reduce the risk, expense, and disruption of software deployment, while promoting the dependability of the software. It does not imply technical support.
Framework Releases
Major framework releases are released every six months (February and August), while minor releases may be released as often as every week. Minor releases should never contain breaking changes.
Using the latest release of the framework provides access to not only the latest security updates, but also new features. Updating your application to the latest release of the framework allows you to take advantage of new features and keeping migrations between subsequent versions relatively straightforward. It’s also an opportunity to refactor code to utilise the functionality of the framework. The work associated with upgrading is incremental, rather than the big jump between LTS versions.
If you follow the installation instructions (https://laravel.com/docs/5.5), you will be downloading the latest release of the framework.
As the question states, I am preparing to deploy my first couple modules on the Magento Connect store and want to make sure I am targeting the best versions. Testing on 1.3 is proving to be a bit of a pain, and if only a few people use that version I would rather spend the time making the modules better!
Google hasn't helped as yet, though I think the keywords I use are getting picked up as other more specific technical questions (Google Base, for example).
Does this information exist? What about your personal experience? For me, I have only encountered installations below 1.5 Community (1.10 Enterprise) for upgrade projects. I haven't personally encountered a client that is on 1.4 and plans to stay on 1.4.
Thanks!
Tim
There are a signification amount of people who have older versions and wont upgrade because of the complexity and the amount of modification they have done to their stores.
Most people right now who are on community version seem to be on 1.5 or 1.6, but if you want to test older versions just download from the archive install locally and see if it works for the older versions.
Here is a link to the downloadable versions of magento, in case you decide to test on those older versions:
http://www.magentocommerce.com/download - click released archived tab at the top