-
Notifications
You must be signed in to change notification settings - Fork 32
[FSSDK-8795]chore: prepare for pre release 4.0.0-beta #515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,64 @@ | ||
# Optimizely Java X SDK Changelog | ||
|
||
## [4.0.0-beta] | ||
May 5th, 2023 | ||
|
||
### New Features | ||
The 4.0.0-beta release introduces a new primary feature, [Advanced Audience Targeting]( https://docs.developers.optimizely.com/feature-experimentation/docs/optimizely-data-platform-advanced-audience-targeting) | ||
enabled through integration with [Optimizely Data Platform (ODP)](https://docs.developers.optimizely.com/optimizely-data-platform/docs) ( | ||
[#474](https://github.com/optimizely/java-sdk/pull/474), | ||
[#481](https://github.com/optimizely/java-sdk/pull/481), | ||
[#482](https://github.com/optimizely/java-sdk/pull/482), | ||
[#483](https://github.com/optimizely/java-sdk/pull/483), | ||
[#484](https://github.com/optimizely/java-sdk/pull/484), | ||
[#485](https://github.com/optimizely/java-sdk/pull/485), | ||
[#487](https://github.com/optimizely/java-sdk/pull/487), | ||
[#489](https://github.com/optimizely/java-sdk/pull/489), | ||
[#490](https://github.com/optimizely/java-sdk/pull/490), | ||
[#494](https://github.com/optimizely/java-sdk/pull/494), | ||
[#495](https://github.com/optimizely/java-sdk/pull/495), | ||
[#496](https://github.com/optimizely/java-sdk/pull/496), | ||
[#497](https://github.com/optimizely/java-sdk/pull/497), | ||
[#498](https://github.com/optimizely/java-sdk/pull/498), | ||
[#500](https://github.com/optimizely/java-sdk/pull/500), | ||
[#501](https://github.com/optimizely/java-sdk/pull/501), | ||
[#502](https://github.com/optimizely/java-sdk/pull/502), | ||
[#503](https://github.com/optimizely/java-sdk/pull/503), | ||
[#504](https://github.com/optimizely/java-sdk/pull/504), | ||
[#509](https://github.com/optimizely/java-sdk/pull/509), | ||
[#511](https://github.com/optimizely/java-sdk/pull/511), | ||
[#512](https://github.com/optimizely/java-sdk/pull/512), | ||
[#513](https://github.com/optimizely/java-sdk/pull/513), | ||
[#514](https://github.com/optimizely/java-sdk/pull/514) | ||
). | ||
|
||
You can use ODP, a high-performance [Customer Data Platform (CDP)]( https://www.optimizely.com/optimization-glossary/customer-data-platform/), to easily create complex | ||
real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important | ||
for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can | ||
be used as a single source of truth for these segments in any Optimizely or 3rd party tool. | ||
|
||
With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and | ||
make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Optimizely Customer Success Manager. | ||
|
||
This version includes the following changes: | ||
- New API added to `OptimizelyUserContext`: | ||
- `fetchQualifiedSegments()`: this API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. The fetched data will be stored in the local cache to avoid repeated network delays. | ||
- When an `OptimizelyUserContext` is created, the SDK will automatically send an identify request to the ODP server to facilitate observing user activities. | ||
- New APIs added to `OptimizelyClient`: | ||
- `sendOdpEvent()`: customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP. | ||
|
||
For details, refer to our documentation pages: | ||
- [Advanced Audience Targeting](https://docs.developers.optimizely.com/feature-experimentation/docs/optimizely-data-platform-advanced-audience-targeting) | ||
- [Server SDK Support](https://docs.developers.optimizely.com/feature-experimentation/v1.0/docs/advanced-audience-targeting-for-server-side-sdks) | ||
- [Initialize Java SDK](https://docs.developers.optimizely.com/feature-experimentation/docs/initialize-sdk-java) | ||
- [OptimizelyUserContext Java SDK](https://docs.developers.optimizely.com/feature-experimentation/docs/optimizelyusercontext-java) | ||
- [Advanced Audience Targeting segment qualification methods](https://docs.developers.optimizely.com/feature-experimentation/docs/advanced-audience-targeting-segment-qualification-methods-java) | ||
- [Send Optimizely Data Platform data using Advanced Audience Targeting](https://docs.developers.optimizely.com/feature-experimentation/docs/send-odp-data-using-advanced-audience-targeting-java) | ||
|
||
### Breaking Changes | ||
- `OdpManager` in the SDK is enabled by default, if initialized using OptimizelyFactory. Unless an ODP account is integrated into the Optimizely projects, most `OdpManager` functions will be ignored. If needed, `OdpManager` to be disabled initialize `OptimizelyClient` without passing `OdpManager`. | ||
- `ProjectConfigManager` interface additions + implementing class updates | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we add more info about this breaking changes (what changes they have to make)? |
||
|
||
## [3.10.3] | ||
March 13th, 2023 | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This list is too long. Can we remove fix PRs (495-514), so can focus on new feature additions.