On Thu, 10 Aug 2023 23:31:57 GMT, Chen Liang <li...@openjdk.org> wrote:
> Just curious, what's the rationale for finalizing the API when there are > significant changes from the last preview? A preview API is finalized when it is ready. The preview process, as outlined by [JEP 12](https://bugs.openjdk.org/browse/JDK-8195734), does not place a mandate on the amount of changes that a JEP that finalizes a preview API should or should not contain. It only requires that the changes since the last preview iteration are noted (which we have done). Though, the amount of changes can be used to inform the decision to finalize. We feel that the FFM API is ready for finalization, and does not require another round of preview. In this case in particular: previous iterations contained significant changes to the API, including re-shuffling of some of the core APIs. (See e.g. https://github.com/openjdk/jdk/pull/13079#issuecomment-1476648707) In contrast this JEP contains mostly superficial changes to the API, that are not likely to impact how a client would write a program using the FFM API. ------------- PR Comment: https://git.openjdk.org/jdk/pull/15103#issuecomment-1675057357
