On Mon, 31 Aug 2026 17:45:36 GMT, Johan Vos <[email protected]> wrote:
>> That's a very good question. Since JavaFX for iOS requires additional >> support that isn't in the repo (meaning, it's not just "use a JDK for that >> platform"), we might consider not including them in the published release >> notes. >> >> @johanvos What do you think? > > I don't think the question about whether or not tested by O. is relevant. > > Apart from that, I don't have a strong opinion. On one hand, I think it is > relevant to indicate that there is ongoing work for platforms that are not in > mainstream releases. On the other hand, I don't want to give the impression > that JavaFX for iOS runs out of the box. > My main reason for including it is that I think we don't want too many rules > about what issues are not in the release notes. Unless there are excellent > reasons that can easily be justified without much discussion, it seems better > to me to have the issues that come out of the filter you and I use in the > release notes. A bit off-topic, my fear is that since we don't test android/iOS, it is possible some of our changes inadvertently break those platforms - something I want to avoid. I am sure you guys deal with the conflicts and the testing on those platforms in a reactive manner, so the release always works. Question - would it make sense to configure the github actions to build on those platforms so we'll have an advance warning when we break things? ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/2256#discussion_r3896969140
