The 1.4.0 version of Capella is now available.
But the current version of M2DOC is not yet compatible.
Does someone know when the new version of M2DOC will be available ?
Thanks
I'm working on it. I will update the Capella section as soon as it's released. It should be done this week. I already updated the corresponding milestone of M2Doc.
Related
I am trying to upgrade Sitecore 9.0 to Sitecore 9.2. Couldn't find any specific way except first upgrading to Sitecore 9.0.2 and then proceed further. But, this way getting many errors related with config file. Is there any other way to upgrade directly to 9.2 verion? Any help would be a highly appreciated. Thanks.
The alternative method to 'upgrade' which I often look to is to spin up a clean install of the newer version and then migrate my old code into a new solution which will already have all the latest configs/ Sitecore base code in place.
Doing this means you can just patch your custom app config settings and ensure the Sitecore dependencies in your solution are the newer version which can often be a cleaner/simpler way to go.
There are a couple of things to consider before doing this however, such as whether you need to keep your data in XDB etc. as it would mean that you may need to look at migrating it which can be a pain and since you are looking at 9.0 to 9.2, you'd have additional services to consider as well such as Identity and may need to account for that kind of thing too.
Problem :
Is it possible to change any information pertaining to the stage-names in BPMN work-flow for previous versions or do we need to deploy a new version for such minor changes?
Not really sure, what you mean by "stage names", but every change to the bpmn xml has to go through deployment to be available on the engine.
You don not have to manually create a new version, camunda will just create a new revision based on same key and version for you.
I have a tool which requires boto3's direct connect functionality. However I cannot tell from which version onwards boto3 includes this functionality.
Is there any way to obtain the older version of the docs to see at which point direct connects were added?
At this point in time the latest is 1.4.4.
boto3 development is an open source initiative. So you can always checkout botocre development repository for the release notes, or ask question there.
changelog.rst will show a brief list of changes.
Then use following command to switch to specify tag version and look for the date of commit.
git checkout tags/<version_name>
I just want to get confirm that will i require another license.xml to upgrade my client sitecore instance from 6.6 to 7.2.
My understanding is sitecore version upgradation do not require any license update.
And, i think license is vendor based which depends upon number of installations and not sitecore version based.
Just want to confirm my self with community experts.
In most scenarios, licenses will apply across 6.6 to 7.2 (or further). However, the only sure way to know is to follow up with your Sitecore sales rep to have them check to see if there are any limits on your license that would prevent you from upgrading to 7.
I'm trying to understand the concept of release chunks from the release matrix page: link
Looking at the ESB480 build instructions, the wording suggests that the release chunks are NOT backward compatible.
To determine which chunk to use for a specific product version, see
the Release Matrix
Question: Are turing release chunks backward compatible? For example, would API Manager 1.5.0 that was released with chunk 2 also run on chunk 5?
Turing platform is a new platform release concept introduced recently. The mail thread "Introducing the Carbon Platform Release Concept" on dev and architecture mailing lists explains this.
As you know, A WSO2 product = WSO2 Carbon + Set of features.
Your question is also about building from source. I know you have an idea about the WSO2 SVN structure and orbit, kernel and platform. You asked those questions :)
As I understand the ESB 4.8.0 Building from Source wiki page suggests that you should checkout relevant chunk release tag.
The release matrix has the information about the each chunk for a specific product.
For example, if you want to build ESB 4.8.0, you should checkout turing-chunk04 tag. To build API Manager 1.5.0, you should checkout turing-chunk02 tag.
Since the platform has all products, you must checkout relevant tag to get the released product.
The backward compatibility depends on each product. For example, the ESB 4.8.0 is not directly compatible with ESB 4.7.0 as the underlying Carbon is a major upgrade and there are user management changes. In such cases you need to migrate data. However the proxies may be compatible.
In general, any turing platform product is not directly backward compatible with a previous version of product with Carbon kernel version < 4.2.0.
Question: Are turing release chunks backward compatible? For example, would API Manager 1.5.0 that was released with chunk 2 also run on chunk 5?
AFAIU, your question is invalid. API Manager 1.5.0 is released under chunk02 and there is no API Manager release under chunk05. However API Manager 1.6.0 is released in Turing chunk 6. So you must checkout turing-chunk06 tag to build the API Manager 1.6.0.
I'm not sure API Manager 1.6.0 is compatible with API Manager 1.5.0. I'm not aware of the changes yet. However I can assure you that there are no changes in the user management and registry tables.
The important factors with Turing platform are that all products are based on Carbon 4.2.0 and there is only one P2 Repository. This means that any turing platform product can install features from a single Turing P2 repository.
I hope this helps to clear out your doubts.
Thanks!