Khoros Communities - Updated Release Process
To improve your experience and simplify our release process, we are updating how we handle Khoros Communities releases. This process will start to apply from Communities Release 25.09. What's Changing Communities will have two types of releases going ahead - Standard releases and Patch releases Standard releases are regular releases that will happen on a cadence during Maintenance Windows. All releases will be standard releases Patch releases are critical bug fixes or security fixes, which happen out-of-band During Standard releases, our teams will automatically upgrade customers on the latest release providing windows for feedback Customers can reach out to support for upgrading legacy instances or for any other feedback Standard Releases We will have a standardized release process for both Aurora and Classic. In a standard release, we will auto-upgrade customers on the latest release. These releases will include features and non-critical bugs. Version numbers for the standard release will follow the existing version numbers. However, we will no longer be treating releases as major or minor - we will treat every release as a standard release. The process will begin when we publish the release notes. The release notes will announce the plan and scope of an upcoming release. After we post the release notes , customers will be notified and have a week to provide feedback to their Customer Representatives on the upcoming release. After this one week, we will upgrade the stage environments. We will open a two-week testing window, where customers can test on their stage environments and provide feedback. Again, Customer Representatives will be the points of contact during this phase. At the end of the two-week window, we will perform the upgrade in production for customers whose stage environments we have successfully upgraded and do not have any open feedback. For both stage and production, we will use existing Maintenance windows, as we expect downtime. If you are on an older version and want to opt back into auto-upgrades, please reach out to your Customer Representative. They can upgrade you to the latest version at any time Patch Releases We will release patches out-of-band for critical bugs that affect multiple customers or affect a release's stability, and security and vulnerability fixes. We will apply patch releases for all customers on the latest version, given that these are critical in nature. Our team will publish the release notes, notify customers and apply patches in a three-day window. Customer Representatives will handle any customer feedback during this phase. Version numbering for patch releases will follow <standard release version number>.<number>, where number will be incremented for each patch and reset after a particular standard version. As an example, the first patch after 25.8 will be numbered 25.8.1, the second patch as 25.8.2 and so on. However, the first patch applied after 25.9 will be 25.9.1. We will use Change windows for non-downtime needs and maintenance windows timeslots for downtime needs. Customer support will notify customers about downtime needs. Customer representatives will reach out if a patch applies to a Customer on an older version. As always, Customer Representatives are available for any feedback. What to expect next As we stabilize and based on feedback on the new release process, we will also be reviewing the cadence of releases which is right now monthly. The intent is to provide high quality releases, minimizing customer disruptions, and allowing customers time to provide feedback and adjust.Khoros Care v25.06.2 Release Notes
The Khoros Care Release version 25.06.1 includes Survey and Welcome Response support for LinkedIn private messages, an increase in the character count of LinkedIn public messages, a new Post Status Escalation tag, and increased visibility of hashtags in agent responses.Khoros Care: Direct Data Access Update
Following our recent efforts to better protect the Khoros Care platform from abnormally high loads and to provide consistency across Care for historical data access directly available, data in Agent View and Manage View will be limited to 2 years. As always, for customers requiring routine access to data beyond that range, we encourage the implementation of local data store using our available export APIs. You may notice this change in effect already. Otherwise, the change will be pushed to your system within the next 10 days.Community Experience Surveys Are Now Available in Aurora
Community Experience Surveys (formerly Value Analytics) enable you to gather responses directly from members through short in-product prompts. You control who sees the survey, when it appears, how often it's shown, and which standardized questions are asked. Once responses start coming in, you can export the results for review or analysis.
