I have Googled about the lastest Version of ignite ui. The only info I got is, it is "2018.2". Is there any place where I can find info about Patches stuff. e.g. I have now Infragistic.Web.Mvc.dll Version 5.18.1.40. Is it the latest one ?
The core portion of the product, which is on GitHub, follows the same versioning, as the full version. You can check all the available versions, as well as the latest one here:
https://github.com/IgniteUI/ignite-ui/releases
Here you can see our Service Release Schedule and all upcoming and current releases for all IG products.
Related
All previous versions, of the various Microsoft.ApplicationInsights.* packages on nuget.org have all switched to being deprecated. This feels unusual for a minor release, and it's not acknowledged in the release notes. Is there a reason for this?
e.g. https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore
To answer my own question for anyone else that might be wondering if they need to upgrade Application Insights packages, the short answer is no. You can keep on using the version you are on with the usual consideration for the patch and minor release notes.
This is a recent move by the Application Insights team to comply with the Azure SDK lifecycle and support policy that states:
or has been superseded by a more recent release. In both cases, the current library is deprecated in favor of a newer library.
The main driver, is that support requests are typically resolved by updating to the latest SDK version, so only 'supporting' the latest version ensures we all try that first before teams commit resources to support.
Source: Application Insights GitHub issue.
Why is 3.2.0 not available here any more? https://downloads.apache.org/spark/
Just to be clear, it was here until a few days ago. This link is checked into our internal repo. Realized this artifact is no longer available when the build broke.
Need to make sure we don't go to prod with this version if there is any known major issue with it that caused it to be taken down.
Download Spark page has only the latest version of every major version of Spark. If you want a specific version not listed on the main downloads page, you can use Archived libraries link.
I am currently using node 6.1 in my project.
I want to upgrade it to latest stable version now.
Before doing that I want to know what are the breaking changes introduced in all the versions in between 6 to 12
Is there any place I can get all these breaking changes for the node versions.
I've found this page to be the most helpful list of all major/minor/patch changes:
https://nodejs.org/en/blog/release/v16.0.0/
Another good resource to find changes to all the different major versions, is the changelog archive on nodejs' github:
https://github.com/nodejs/node/tree/main/doc/changelogs
We have SAP Hybris Commerce version 5.1.1 with custom extensions installed. Now we need to upgrade it to newest version 6.2.
My question is: Can we upgrade it to 6.2 and skip all versions between 5.1 and 6.2? Or must it be done by upgrading to 5.2, then to 5.3 and so on?
Yep - 5.1.1 to 6.2 ought to work (I've been working on a project that's done exactly this).
You will probably have to make some changes - watch out for any customisations you've made - it might be worth reading through the release docs to have an idea of what's changed - off the top of my head the structure of add ons is one area that's a bit different between 5.1 and 6.2, but otherwise things should work OK in theory.
Yes you can directly update to 6.2.
It's important to regulary update your hybris version. You should not have so much gap with current version. Indeed it become tougher to migrate your custom code.
Upgrading each minor version in a row is totally useless most of the time. Only do this if you have issues you can't solve while migrating to the target version.
You should take a look at this migration documentation and this guide (it can be used even if it doesn't match your version).
Note that some stuff like promotion are totally different in hybris 6 so you can expect some trouble to migrate everything. Take care of your extensions generated with old template also.
5.5.1 introduces JDK8 and Spring 4, I would not underestimate this change! Depending on the size of your project I would first go for 5.5.1. Also notice the MySQL change for 6.2 (5.6). Don't forget to declare deployment tables in your items.xml. Search for "third-party compatibility" and "release notes" on the wiki. Also try shifting to the backoffice since the hMC is marked as deprecated.
Yes you can migrate directly 6.2.
The time and difficulty depends on your custom code (and how much it respects good practices : naming conventions, usage of service, architecture respect...etc)
You might also consider that HMC is deprecated in 6.2
I installed the Achecker from http://www.atutor.ca/achecker/
and ran the guidelines to get a report.
Earlier we were doing the same with http://Achecker.ca
There are few guidelines are missing in the local version. They are not similar. Is there any difference and if yes is there a way to upgrade the techniques to latest on the local version.
The version from the Web site is the Achecker version 1.3 (25/11/2011).
See sourceforge history here:http://sourceforge.net/projects/achecker/files/achecker/
You can find on GitHub, a version of June 2014:
https://github.com/inclusive-design/AChecker