Kevin is correct. The specification committee ballot is concerned with a project level event (release/review). For projects that include more than one specification, a single release/review is the expectation. This is what we did during the first round of ballots.
I was hoping for some feedback from the specification committee that the descriptions of the releases are sufficient before calling the ballot. That is, is 'First release going through the JESP. Bug fix release of 2.3.2. This service release includes an update to the Jakarta XML Web Services 2.3 Specification, Jakarta SOAP Attachments 1.4 Specification and Jakarta Web Services Metadata 2.1 Specification." enough for the specification committee members to vote on? What more does the specification committee want to see? For an answer to that, we (or, more specifically, the project team) really need to engage the specification committee (e.g., David started a
discussion regarding the Jakarta Enterprise Beans project release)
According to the JESP, we need 14 days to run a ballot for a service release, so I need to call that ballot today (or tomorrow at the latest) if we want to release on February 19.
Wayne