| [jakarta.ee-spec.committee] EJB 4.0 Ballot material issue |
Spec. Committee:
A comment was made in the Spec. committee meeting this morning that concerned me ... Every final Spec. ballot must include a CCR that validates that the Spec. requirements have been fulfilled by an implementation (which, upon final approval will become a "compatible implementation" of that Spec).
I checked -- The EJB 4.0 PR did include a CCR. That CCR was
originally filed against the wrong project. This was noted in the
CCR. After the ballot concluded, a replacement CCR issue was
created and closed on the same day in the EJB-API repository. The
original CCR was then marked "invalid," after the ballot was
closed. The EJB PR text was never updated to correct this late
change.
I updated the EJB PR comments to point to the correct CCR issue.
In the future, I might suggest we use the "Transfer issue" feature if something like this happens again. That will simply move the issue from one repository to another. If repository access permissions are an issue, I'm sure we can always find someone who has enough permissions -- worst case, an Eclipse Admin could be called in to make the switch.
I trust that's all okay with everyone -- though I can see that
the process may not have actually held up well in this set of
actions.
Thanks,
-- Ed