This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hello Andy,
thanks for your response. Please find attached an example for App Connect Operator. the operator was supported on s390x environment till version 6.1 , then v6.2,v7.0,v7.1,v7.2 of the operator were not available on s390 environment then the environment was supported again for version v8.0
In this case, and before the release of v8.0, if the client knew that the max supported version for 390 was v6.1 it would have been useful before the installation and without checking the documentation. and the preference for the notification is to have it like a push notification or email so that the client team wouldn't have to check the documentation on a regular basis.
Hi Karen,
Thanks for raising this - one of the reasons that we don't currently specify the maximum version is for flexibility - if we're not aware of any restrictions in future versions then we don't want to force users to have to update operators if they are still compatible with the future release (e.g. CP4I aims to support even numbered versions of OpenShift within 30 days - if the current version supports it with no updates, then users can carry on using it)
Do you have examples of issues that this has caused so we can better understand the impact please?
On your second point about notification, in an 'online' installation, then there should be notifications about updates as long as the subscription settings are not locked down.
Are you wanting updates through the platform itself or through some other method e.g. an email subscription/notification? Again, just wanting to understand the use case further.