[jakarta.ee-spec.committee] Couple of observations re: EE 10 PRs

[Ed Bratt <ed.bratt@xxxxxxxxxx>]

Hi,

I've just reviewed all the EE 10 Plan proposal pages along with the 
Release Review pages that have been created.  A couple of things came to 
mind as I was going through these. I'm hoping there's some consensus 
about these observations.

First: All Specifications except for Activation should remember to 
change their last copyright date to 2022.

Second: Many of the EE 10 proposals are rather vague with respect to 
exactly what features and fixes they were going to take on for EE 10. 
Especially for these proposals, but probably for all projects -- the 
release review PR should include text details for a reader to learn 
exactly what changes were made from the previous Spec. release -- this 
might be a bug-list link -- or perhaps just text describing / 
highlighting the primary changes. I think it was perfectly appropriate 
that the Plan review text might have been somewhat vague, but the 
release review text should have a clear summary of the changes (at least 
the highlights). Even for the cases where the plan proposal text clearly 
identifies specific goals, the release review text should be revised to 
describe what was actually done (Perhaps the PR thread itself might be 
useful for documenting things that were on the original list but didn't 
actually make the final release cut. Not totally sure about that.)

As an example, I'd hope that the final Spec. update text would not 
include "Bug fixes and enhancements as requested by the community." It 
might be okay to pick an issue or two and then just refer the reader to 
the GitHub release text (or the PMI change log ... whichever the project 
team prefers).

I'd like to get agreement about what we want to set our review goals for 
so we can leave a consistent record, once we've finished up EE 10.

Thanks,

-- Ed