[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] Will Milestone TCKs be signed?
|
I don't intend to do that for our TCKs and I don't see a point as a signed TCK is only relevant for validation to make a compatibility claim. That really should not be possible.
HI,
Do we intend for the Jakarta EE 9 Milestone TCKs to be signed and posted
through the same finalization process as we did for final TCKs, as in
Jakarta EE 8?
(the php signature value is computed. The SHA256 is computed. These and
the TCK are promoted into:
https://download.eclipse.org/jakartaee/<spec>/<version>/<name>.zip,
<name>.zip.sha256, and <name>.zip.sig)
To me, this seems like a complication we don't necessarily need.
Personally, I would be fine with the TCKs pushed to a public location
perhaps including a SHA256 to allow users to verify as needed.
Anyone have thoughts on this, one way or another? Maybe this was decided
already?
-- Ed
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
