Here's my first guess at repos where the EE4J_8 branch has not been merged:
authentication: NOT MERGED
authorization: NOT MERGED
bvtck-porting: NOT MERGED
cdi: NOT MERGED
cdi-tck: NOT MERGED
cditck-porting: NOT MERGED
common-annotations-api: NOT MERGED
concurrency-api: NOT MERGED
concurrency-ri: NOT MERGED
ditck-porting: NOT MERGED
ejb-api: NOT MERGED
enterprise-deployment: NOT MERGED
glassfish-maven-embedded-plugin: NOT MERGED
glassfish-security-plugin: NOT MERGED
grizzly: NOT MERGED
grizzly-ahc: NOT MERGED
grizzly-memcached: NOT MERGED
grizzly-npn: NOT MERGED
grizzly-thrift: NOT MERGED
interceptor-api: NOT MERGED
jakartaee-firstcup-examples: NOT MERGED
jakartaee-schemas: NOT MERGED
jakartaee-tutorial-examples: NOT MERGED
jax-rpc-api: NOT MERGED
jax-rpc-ri: NOT MERGED
jax-ws-api: NOT MERGED
jaxb-api: NOT MERGED
jaxb-dtd-parser: NOT MERGED
jaxb-fi: NOT MERGED
jaxb-istack-commons: NOT MERGED
jaxb-ri: NOT MERGED
jaxb-stax-ex: NOT MERGED
jaxr-api: NOT MERGED
jaxr-ri: NOT MERGED
jca-api: NOT MERGED
jersey: NOT MERGED
jms-api: NOT MERGED
jpa-api: NOT MERGED
jsonb-api: NOT MERGED
jsonp: NOT MERGED
jsp-api: NOT MERGED
jstl-api: NOT MERGED
jta-api: NOT MERGED
jws-api: NOT MERGED
management-api: NOT MERGED
metro-jax-ws: NOT MERGED
metro-jwsdp-samples: NOT MERGED
metro-mimepull: NOT MERGED
metro-package-rename-task: NOT MERGED
metro-policy: NOT MERGED
metro-saaj: NOT MERGED
metro-ws-test-harness: NOT MERGED
metro-wsit: NOT MERGED
metro-xmlstreambuffer: NOT MERGED
mojarra: NOT MERGED
mojarra-jsf-extensions: NOT MERGED
openmq: NOT MERGED
orb: NOT MERGED
orb-gmbal: NOT MERGED
orb-gmbal-commons: NOT MERGED
orb-gmbal-pfl: NOT MERGED
saaj-api: NOT MERGED
servlet-api: NOT MERGED
soteria: NOT MERGED
websocket-api: NOT MERGED
yasson: NOT MERGED
Bill Shannon wrote on 3/4/20 8:48 AM:
It turns out there's a lot of repos that still have EE4J_8 branches. Here's the list:
I assume most of them have been merged into master. (I could probably figure that out with a bit more git hacking.) But clearly people aren't deleting them.
Kevin Sutter wrote on 3/4/20 7:17 AM:
Bill had suggested something similar... But, my take is that most (all?) of the Projects were already aware of this exercise and I consider JSTL a special case. If this notice to
the Spec Projects creates a lot of "of my, I forgot to do that" type of comment, then I guess we'll have to be more diligent. But, I really hope this was just a public service announcement that the Projects can just say "been there, done that"...
---------------------------------------------------
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
Do you want to track it somehow? For instance, should we delete EE4J_8 branches (not my preference) or add a note on a github project when it is complete?
On Wed, 4 Mar 2020 at 14:29, Kevin Sutter <sutter@xxxxxxxxxx>
wrote: Hi,
Just a heads up... As we were working through the JTSL project, we found that the old EE4J_8 project was never properly merged with Master. Since this Project is kind of an "orphan", I'm hoping that this is the only case of these forgotten changes. We now
have this project cleaned up and ready to produce the Milestone API artifact. But, Bill and I thought it would be a good idea to remind all of the Specification Projects to ensure that any Jakarta EE 8 work was properly merged into Master before getting too
far down the Jakarta EE 9 path. Thanks!