Skip to content

Polish 3.8.0 release notes.#444

Merged
RichardSmedley merged 1 commit intorelease/3.8from
polish-3.8.0-release-notes
Apr 16, 2025
Merged

Polish 3.8.0 release notes.#444
RichardSmedley merged 1 commit intorelease/3.8from
polish-3.8.0-release-notes

Conversation

@dnault
Copy link
Contributor

@dnault dnault commented Apr 15, 2025

Remove references to PREFERRED_SERVER_GROUP_OR_ALL_AVAILABLE, since it is not exposed to users.

Add important details to the descriptions of JCBC-2183 (the external name for this feature is "get multi") and JCBC-2186 (describe the change to the API).

Remove references to `PREFERRED_SERVER_GROUP_OR_ALL_AVAILABLE`,
since it is not exposed to users.

Add important details to the descriptions of JCBC-2183
(the external name for this feature is "get multi")
and JCBC-2186 (describe the change to the API).
Copy link
Contributor

@RichardSmedley RichardSmedley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@RichardSmedley RichardSmedley merged commit 525929c into release/3.8 Apr 16, 2025
5 of 7 checks passed
@RichardSmedley RichardSmedley deleted the polish-3.8.0-release-notes branch April 16, 2025 09:21
@programmatix
Copy link
Contributor

programmatix commented Apr 16, 2025

I was wondering if this was my messup, but I did set a relnotes field on JCBC-2183.

For JCBC-2147, what's the best way of indicating that is an internal change not for the relnote?

@RichardSmedley
Copy link
Contributor

RichardSmedley commented Apr 16, 2025

I was wondering if this was my messup, but I did set a relnotes field on JCBC-2183.

For JCBC-2147, what's the best way of indicating that is an internal change not for the relnote?

Given recent discussion, looks like a token in the release-notes field would be best?
(A human-readable one at that)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants