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.
Related
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.
I currently use Siebel version 8.1.1.11, I would like to upgrade version 21.2 or 21.4 version. Have you ever been partake of something this experience. If so that, is there any tools to this upgrade? Can you share your experience?
Thanks for help
Based on my experience, this operation is complicated if there are many customizations are made in the version 8.1.1.11 in order to meet the requirements of version 21.2 or 21.4 and mostly needs long-term project to implement the upgrade and minimize the number of possible issues. However, if the current version has little customizations. Then, there might be a chance to upgrade, but still the gap is big between the two versions.
We will be developing a new web site for a client who already has a Kentico 8.2 license. I am trying to make a case for developing the site using Kentico 9. Some key features I have found so far include:
faster performance (how much in real-world terms?)
better integration with .Net MVC
content staging tasks can be synchronized per user account
better rollback functionality: previously we had to make full database backups, content staging in Kentico 8.2 causes issues for restoring previous versions of a page.
built in source control support for GIT
It looks like Kentico integration with the client's existing database may be possible. Has anyone done this? What are the limitations or caveats?
Is there a discount for upgrading the license from 8.2 to 9?
Thanks in advance for your feedback!
faster performance (how much in real-world terms?)
there are major (official) improvements for content and contact management
better integration with .Net MVC
there is whole new way to develop sites using ASP.NET MVC with Kentico
content staging tasks can be synchronized per user account
there is pretty good blogpost describing new staging improvements
better rollback functionality: previously we had to make full database
backups, content staging in Kentico 8.2 causes issues for restoring
previous versions of a page.
I am not sure what do you mean by new rollback functionality
built in source control support for GIT
you might confused with continuous integration feature
You can find release notes with all new features and improvements here.
It looks like Kentico integration with the client's existing database
may be possible. Has anyone done this? What are the limitations or
caveats?
there is tested upgrade utility for upgrading to Kentico 9
Is there a discount for upgrading the license from 8.2 to 9?
for pricing you should definitely contact Kentico sales department
See the answer I posted on the DevNet (which by the way, no need to cross-post on both)
If they have a license for 8.2, is their maintenance current? If so, simply go to the client portal and upgrade it for free. This can be done without any cost. Either way, the licensing cost doesn't come from the version, it comes from the type (base, ultimate, ems, etc.).
So assuming they purchased their license about a year ago, their maintenance should be current or close to current and you either get current on your maintenance or just go to the client portal and see if it will allow you to upgrade your license and get a new key for v9.
If they don't have the site built, there is no reason to build it on v8.2 at all.
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
I was wondering, how often does DHTMLX offer a new version and how hard do you find it to upgrade your applications to the new version. This is namely a critical part in my research, but I cant seem to find any problems with updates. This question is just to make sure that my findings are correct.
Please suffice with: version number, DHTMLX component.
I work for DHTMLX. During the past 3 years we released one major update per year. Currently we're preparing the next version which we hope will be available in beta till the end of April 2012. We try to make the new releases backwards compatible and provide the upgrade path to the latest release (like here).
I've used many controls from the dhtmlxsuite in our app for the past 5 yrs. They are pretty good at making things backwards compatible, but not always. When going from v3 to v4 just a few months ago, there was quite a lot I had to do get my code back up and running. Also there dropped a few features that were supported in v3, this is not so good in my opinion. But overall, I really like the dhtmlx controls, they are an integral part of our product which now is used all over the world by thousands of users (http://www.ecosys.net/ecosys-epc/).