[JDK-8279396] Define version in .jcheck/conf - Java Bug System

Type: Task
Resolution: Fixed
Priority: P3
Fix Version/s: jfx18
Affects Version/s: jfx11, jfx17, jfx18
Component/s: javafx
Labels:
- noreg-cleanup
- sn_109

Subcomponent:
other

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8279458	jfx17.0.2	Kevin Rushforth	P3	Resolved	Fixed
JDK-8279455	jfx11.0.14	Kevin Rushforth	P3	Resolved	Fixed

This is the JavaFX equivalent of ~~JDK-8279223~~.

We should define the JBS "version" field in .jcheck/conf instead of tracking "fixversion" in the Skara bot configuration.

This will reduce the timing and complexity needed when starting new JavaFX releases. We are already defining the version numbers used in the build in build.properties, so we already know this isn't causing merge issues. Updating this file as well will not add much to the new release change.

I will update the instructions in `UPDATING-VERSION.md`.

Once done in mainline, I intend to also backport this to all active update releases.

backported by

JDK-8279455 Define version in .jcheck/conf

Resolved

JDK-8279458 Define version in .jcheck/conf

Resolved

relates to

JDK-8286018 Create README file to document bumping the version number

Closed

JDK-8279223 Define version in .jcheck/conf

Resolved

links to

Commit openjdk/jfx11u/e8066068

Commit openjdk/jfx17u/b6b7207a

Commit openjdk/jfx/1feba1f6

Review openjdk/jfx11u/68

Review openjdk/jfx17u/27

Review openjdk/jfx/706

(5 links to)

Loading...

Type: Task
Resolution: Fixed
Priority: P3
Fix Version/s: jfx18
Affects Version/s: jfx11, jfx17, jfx18
Component/s: javafx
Labels:
- noreg-cleanup
- sn_109

Subcomponent:
other

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8279458	jfx17.0.2	Kevin Rushforth	P3	Resolved	Fixed
JDK-8279455	jfx11.0.14	Kevin Rushforth	P3	Resolved	Fixed

This is the JavaFX equivalent of ~~JDK-8279223~~.

We should define the JBS "version" field in .jcheck/conf instead of tracking "fixversion" in the Skara bot configuration.

This will reduce the timing and complexity needed when starting new JavaFX releases. We are already defining the version numbers used in the build in build.properties, so we already know this isn't causing merge issues. Updating this file as well will not add much to the new release change.

I will update the instructions in `UPDATING-VERSION.md`.

Once done in mainline, I intend to also backport this to all active update releases.