Staging to the Concurrency project is fine with me. To report the TCK results, we just need to list a link to staging somewhere (and the SHA).
From: cu-dev <cu-dev-bounces@xxxxxxxxxxx> on behalf of "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
Reply-To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Date: Monday, April 25, 2022 at 10:08 AM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [cu-dev] Gitlab issue for uploads
It can be staged in the project directory I believe From: cu-dev <cu-dev-bounces@xxxxxxxxxxx> On Behalf Of arjan tijms Sent: 25 April 2022 16:07 To: cu developer
discussions <cu-dev@xxxxxxxxxxx>
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
It can be staged in the project directory I believe
From: cu-dev <cu-dev-bounces@xxxxxxxxxxx>
On Behalf Of arjan tijms
Sent: 25 April 2022 16:07
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: Re: [cu-dev] Gitlab issue for uploads
If it isn't we'll notice it soon enough. I think it was in the spec committee that David Blevins talked about this.
Anyway, the next hurdle is we have read permission, but no write permissions in the TCK folder:
drwxr-sr-x 2 genie.jakartaee-tck ee4j.jakartaee-tck 4096 Apr 21 11:41 .
Only user "genie.jakartaee-tck" can write.
|