The spec PR includes the staged TCK URL.
Presumably the cert request will be longer lived than the spec PR
and the staged TCK URL, so it includes the final URL. Ditto the TCK
results, which are supposed to have a copy of the cert request.
Scott Stark wrote on 8/15/19 9:32 AM:
So the disconnect is that some cert requests are using the
hypothetical final TCK URL. Not all are doing that. For the
initial CI being used to validate a spec, that frankly does not
make sense to me as it cannot be verified.
You were
all quite
busy last night on this topic... Although it seems like
we're nearing
a compromise, I tend to agree with Bill that we have more
important things
to be concerned with. Yes, we have a branding issue of
the TCKs.
If David figures out some magic or we just duplicate the
entries
as Bill suggests, I'm okay with correcting the problem.
But, we can
not re-spin all of the PRs that are already in the ballot
queue...
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx
Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
Bill
Shannon <bill.shannon@xxxxxxxxxx>
To:
Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>,
David Blevins <dblevins@xxxxxxxxxxxxx>
Date:
08/15/2019
01:08 AM
Subject:
[EXTERNAL]
Re: [jakarta.ee-spec.committee] eclipse-* -> jakarta-*
for TCK zip files
Sent
by: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx
A short
term hack would be to make
them available at both names. The jakarta.ee
pages can be updated to link to the jakarta-* names and
all the other pages
can continue to link to them at the eclipse-* names.
David Blevins wrote on 8/14/19 8:16 PM:
> Let's retire this conversation for now with the
mutual understanding
that anything that would result TCK summaries or
certification requests
to be broken is a showstopper.
>
> I'm working on the promotion script now and facing
unrelated issues
with bash syntax differences. Once I'm done, I can
throw in a livable
solution for the filenames in less time than I can write
an email.
>
> This will not be a problem.
>
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|