[jakarta.ee-spec.committee] Where to raise issue regarding read access t

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jakarta.ee-spec.committee] Where to raise issue regarding read access to every Jakarta CI for committers

From: Scott Stark <sstark@xxxxxxxxxx>
Date: Tue, 5 Nov 2019 19:13:24 -0600
Delivered-to: jakarta.ee-spec.committee@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jakarta.ee-spec.committee>
List-help: <mailto:jakarta.ee-spec.committee-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee>, <mailto:jakarta.ee-spec.committee-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jakarta.ee-spec.committee>, <mailto:jakarta.ee-spec.committee-request@eclipse.org?subject=unsubscribe>

One of the main problems with the Jakarta EE 8 release was the
inability to share/view CI TCK and release job configurations across
projects due to visibility restrictions to the CI job configurations.
One thing we brought up needing to look into was providing read access
to all Jakarta projects CI jobs to committers on any project. Where
would I raise this issue to start tracking it?

Prev by Date: [jakarta.ee-spec.committee] Plan Review
Next by Date: [jakarta.ee-spec.committee] Jakarta-ized Specs a requirement for Jakarta EE 9?
Previous by thread: [jakarta.ee-spec.committee] Plan Review
Next by thread: [jakarta.ee-spec.committee] Jakarta-ized Specs a requirement for Jakarta EE 9?
Index(es):
- Date
- Thread

Breadcrumbs