Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8303363 | jfx21 | Kevin Rushforth | P2 | Resolved | Fixed | b07 |
JDK-8303364 | jfx17.0.7 | Kevin Rushforth | P2 | Resolved | Fixed | |
JDK-8303365 | jfx11.0.19 | Kevin Rushforth | P2 | Resolved | Fixed | b01 |
For example:
openjfx20 --> jfx20
openjfx21 --> jfx21
openjfx17.0.7 --> jfx17.0.7
openjfx11.0.19 --> jfx11.0.19
...
We need to update the JBS version in .jcheck/conf in each active code line: jfx (mainline), jfx17u, jfx11u.
The planned cut-over date is Tuesday, Feb 28. I will prepare PRs for jfx:master, jfx:jfx20, jfx17u:master, and jfx11u:master to update the JBS version field in .jcheck/conf for all active code lines and integrate them immediately after the JBS version renaming is done.
Note that creating separate PRs targeted to jfx:master and jfx:jfx20 is a necessary exception to the usual rule where a fix goes into one or the other. In this case it needs to go into both so that they can be integrated immediately after the version change. The merge will have conflicts anyway, since the jbs fix versions are already different in the two branches, and doing it this way will allow a trivial resolution of the eventual merge conflict (which doesn't then have to be done urgently).
- backported by
-
JDK-8303363 Change JBS version in .jcheck/conf to jfxNN[.0.MM]
- Resolved
-
JDK-8303364 Change JBS version in .jcheck/conf to jfxNN[.0.MM]
- Resolved
-
JDK-8303365 Change JBS version in .jcheck/conf to jfxNN[.0.MM]
- Resolved
- links to
-
Commit openjdk/jfx11u/275147a8
-
Commit openjdk/jfx17u/19cb7c70
-
Commit openjdk/jfx/17ea0573
-
Commit openjdk/jfx/e44e0dc2
-
Review openjdk/jfx11u/134
-
Review openjdk/jfx17u/114
-
Review openjdk/jfx/1034
-
Review openjdk/jfx/1035