to avoid confusion over how the pool values are managed the following updates to the way Skara handles pool values are proposed:
Expected behavior:
N-pool only matches release versions N.0.m
N-pool-oracle only matches release versions N.0.m-oracle
Changes required:
Need changes in 8 (for a new 8-pool-oracle version)
Need changes in 11 and above as at the moment N-pool will be consumed by N.0.m or N.0.m-oracle
While we're not quite reversing https://bugs.openjdk.org/browse/SKARA-1626 this would constitute a change in behaviour that supersedes that issue.
all confidential issues with 8-pool will be moved to 8-pool-oracle
there are around 100 open issues
https://bugs.openjdk.org/issues/?jql=project%20%3D%20jdk%20and%20fixversion%20%3D%208-pool%20and%20resolution%20is%20empty%20and%20level%20is%20empty
that will need to be updated taking into account who owns the issue
Expected behavior:
N-pool only matches release versions N.0.m
N-pool-oracle only matches release versions N.0.m-oracle
Changes required:
Need changes in 8 (for a new 8-pool-oracle version)
Need changes in 11 and above as at the moment N-pool will be consumed by N.0.m or N.0.m-oracle
While we're not quite reversing https://bugs.openjdk.org/browse/SKARA-1626 this would constitute a change in behaviour that supersedes that issue.
all confidential issues with 8-pool will be moved to 8-pool-oracle
there are around 100 open issues
https://bugs.openjdk.org/issues/?jql=project%20%3D%20jdk%20and%20fixversion%20%3D%208-pool%20and%20resolution%20is%20empty%20and%20level%20is%20empty
that will need to be updated taking into account who owns the issue