[jakarta.ee-spec.committee] Version control on the EE4J Release Records

["Kevin Sutter" <sutter@xxxxxxxxxx>]

At today's Spec call,
Wayne mentioned that the Release Records could have version control enabled.
 I'd like to explore that possibility a bit...  Since none of
our projects have this enabled, how would this work?  Are there any
examples of projects that use the version control on their release records
that we could view?  Or, maybe a mock up on one of our projects to
experiment with?

At a minimum,
it might be nice to lock down a release record when we have completed a
successful ballot.  We record the ballot results in the Specifications
repo.  But, where do we record the actual release plan that we approved?
 We discussed the storing of release plans in github like the Platform
and EJB are doing.  But, locking down the content of the Activation
release record after the ballot passes might be nice.  As David pointed
out -- for historical reference purposes.

So, I'm wondering
what type of mechanisms we might already have in place versus what might
need to be developed.  I'm just looking for something simple.  Thanks!

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter