Nobody objected to these descriptions so I added them to the operations
document as a table (at the end). I noticed that some of the
certification requests aren't using the required "certification"
label because it hasn't been added to the issue tracker. I added
this to the checklist.
BTW, where are we with having the specification-committee repo
content appear on the jakarta.ee web site?
Bill Shannon wrote on 7/26/19 2:53 PM:
I used these descriptions:
challenge - TCK challenge
accepted - Accepted certification request
challenge-appeal - Appeal a rejected TCK challenge
appealed-challenge - TCK challenge was appealed
certification - Compatibility certification request
These already existed and I didn't change them:
invalid - This doesn't seem right
enhancement - New feature or request
Bill Shannon wrote on 7/26/19 2:44
PM:
Are there descriptions to go with each of those?
Scott Stark wrote on 7/26/19 2:32
PM:
Yes, the https://github.com/jakartaee/specification-committee/blob/master/operations.adoc has
them at the end:
The current TCK challenge and
compatibility request process requires the following
issue labels:
-
challenge
-
accepted
-
challenge-appeal
-
appealed-challenge
-
invalid
-
enhancement
-
certification
_______________________________________________
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
|
