On Mon, 31 Aug 2026 17:53:55 GMT, Andy Goryachev <[email protected]> wrote:
>> 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? > > Speaking of the release notes, would it make sense to have a separate section > that talks about android/iOS specifics, or you would rather not? > I don't think the question about whether or not tested by O. is relevant. You're right, it isn't relevant (and my answer ignored that specific part of Andy's question). > 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. Yes, this is the question. > 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. I wasn't suggesting to add more rules. Rather the question is "should we add `javafx-rn-exclude` label to explicitly exclude them" like I do for other issues that don't make sense for the release notes. Currently they are not excluded which is why they are in this PR. I'm OK either way, but since iOS releases really are separate, it's worth asking the question. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/2256#discussion_r3897054201
