The information you provide here will be included in the Open Liberty GA release blog post (example), which will be published on openliberty.io/blog/, and potentially elsewhere, to promote this newly released feature/function of Open Liberty. For this post to be included in the GA issue please make sure that this is completed by the end of Friday following the GM (Wednesday). The beta and release blogs are created using automation and rely on you following the template's structure. DO NOT REMOVE/ALTER THE <GHA> TAGS THROUGHOUT THIS TEMPLATE.
Please provide the following information:
If this was previously published in a beta blog post, then provide the link to that OpenLiberty/open-liberty beta blog post issue on the next line between the <GHA-BLOG-BETA-LINK> tags. If nothing has changed since the beta, you're done and can omit the remaining steps. If you need to make updates/alterations to the beta content, then do all the steps.
https://github.com/OpenLiberty/open-liberty/issues/0
N/A This is a new feature.
2. Which Liberty feature(s) does your update relate to?
Human-readable name (eg WebSockets feature):
> Adding the Partitioned cookie attribute.
3. Who is the target persona? Who do you expect to use the update? eg application developer, operations.
> application developers, application server administrators
4. Provide a summary of the update, including the following points:
> A new cookie attribute ("Partitioned") is needed to keep sites functioning after chromium-based browsers start blocking third party cookies later this year.
Partitioned will only applies to cookies marked as SameSite=None since only they can be shared in cross-site requests.
Three new properties are added to Liberty to allow easy configuration for any cookies which need to be partitioned.
More information can be found here:
- https://developers.google.com/privacy-sandbox/3pcd/chips
- https://github.com/privacycg/CHIPS
- https://developer.mozilla.org/en-US/docs/Web/Privacy/Privacy_sandbox/Partitioned_cookies
What happens next?
Add the label for the GA you're targeting: target:YY00X.
Make sure this blog post is linked back to the Epic for this feature/function.
Your paragraph will be included in the GA release blog post. It might be edited for style and consistency.
You will be asked to review a draft before publication.
Once you've approved the code review, close this issue.
If you would also like to write a standalone blog post about your update (highly recommended), raise an issue on the Open Liberty blogs repo. State in the issue that the blog post relates to a specific release so that we can ensure it is published on an appropriate date (it won't be the same day as the GA blog post).
volosied
commented
2 weeks ago
The information you provide here will be included in the Open Liberty GA release blog post (example), which will be published on openliberty.io/blog/, and potentially elsewhere, to promote this newly released feature/function of Open Liberty. For this post to be included in the GA issue please make sure that this is completed by the end of Friday following the GM (Wednesday). The beta and release blogs are created using automation and rely on you following the template's structure. DO NOT REMOVE/ALTER THE
<GHA>TAGS THROUGHOUT THIS TEMPLATE.Please provide the following information:
OpenLiberty/open-libertybeta blog post issue on the next line between the<GHA-BLOG-BETA-LINK>tags. If nothing has changed since the beta, you're done and can omit the remaining steps. If you need to make updates/alterations to the beta content, then do all the steps.What happens next?
target:YY00X.