Hi,
Daniel P. Berrangé <berrange(a)redhat.com> writes:
One way to reduce this burden is to not introduce new JDKs to all
existing Fedora streams, only add it to rawhide so certification is
only needed once.
Having said that I'm still not clear on the real impact of the
certification. Presumably thue certification is not re-done in each
JDK RPM re-build, nor on every RPM re-build of a library it depends
on. If so, then do we really need to do certification for every
Fedora release stream when adding a new JDK. Can we do a build for
35, certify it, and then do what is effectively no-change import
and rebuild for 36/37-rawhide and just consider the 35-certification
to cover those streams.
As I understand it, the certification (TCK) is only done on a binary
level, and only applies to the OpenJDK package itself. It's not a
one-time thing when a new version of the OpenJDK is added; it needs to
be re-done on every single rebuild and/or update of OpenJDK.
AFAIK, even if you rebuild the exact same sources with the exact same
toolchain with the exact same compiler flags, you still can't claim TCK
certification status from one build carries over to the next.
If we import a binary (RPM) from one Fedora version to the other, then
we can continue claiming that the original binary is still certified.
Please note that it has been more than 5 years since I was last involved
with Java, so things might have changed. I might also be mis-remembering
something. But hopefully that gives some context on why the
certification (TCK) burden is so huge.
Omair
--
PGP Key: B157A9F0 (
http://pgp.mit.edu/)
Fingerprint = 9DB5 2F0B FD3E C239 E108 E7BD DF99 7AF8 B157 A9F0