Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-spec-project-leads] Merging of EE4J_8 branches?

Although it's probably a good practice to delete these old branches, there's no firm requirement to do so.  So, the existence of these EE4J_8 branches doesn't necessarily mean there's a problem.

One additional observation...  I specifically only sent this note to the Specification Projects.  I didn't send it to the Implementation Projects, so some of the repos below are not getting this discussion...  Not sure if we have to expand the distribution of this string of notes.  Or, we could leave it up to each Spec Project to communicate this to the respective Implementation projects (my preference).

---------------------------------------------------
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



From:        Bill Shannon <bill.shannon@xxxxxxxxxx>
To:        JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>, Kevin Sutter <sutter@xxxxxxxxxx>
Date:        03/04/2020 10:56
Subject:        [EXTERNAL] Re: [jakartaee-spec-project-leads] Merging of EE4J_8 branches?




It turns out there's a lot of repos that still have EE4J_8 branches.  Here's the list:

authentication
authorization
bvtck-porting
cdi
cdi-tck
cditck-porting
common-annotations-api
concurrency-api
concurrency-ri
ditck-porting
ejb-api
el-ri
enterprise-deployment
glassfish-maven-embedded-plugin
glassfish-security-plugin
grizzly
grizzly-ahc
grizzly-memcached
grizzly-npn
grizzly-thrift
interceptor-api
jakartaee-firstcup-examples
jakartaee-schemas
jakartaee-tutorial-examples
jax-rpc-api
jax-rpc-ri
jax-ws-api
jaxb-api
jaxb-dtd-parser
jaxb-fi
jaxb-istack-commons
jaxb-ri
jaxb-stax-ex
jaxr-api
jaxr-ri
jca-api
jersey
jms-api
jpa-api
jsonb-api
jsonp
jsp-api
jstl-api
jta-api
jws-api
management-api
metro-jax-ws
metro-jwsdp-samples
metro-mimepull
metro-package-rename-task
metro-policy
metro-saaj
metro-ws-test-harness
metro-wsit
metro-xmlstreambuffer
mojarra
mojarra-jsf-extensions
openmq
orb
orb-gmbal
orb-gmbal-commons
orb-gmbal-pfl
saaj-api
security-api
servlet-api
soteria
websocket-api
yasson

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



From:        
Tom Jenkinson <tom.jenkinson@xxxxxxxxxx>
To:        
JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Date:        
03/04/2020 08:49
Subject:        
[EXTERNAL] Re: [jakartaee-spec-project-leads] Merging of EE4J_8 branches?
Sent by:        
jakartaee-spec-project-leads-bounces@xxxxxxxxxxx




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!

---------------------------------------------------
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
_______________________________________________
jakartaee-spec-project-leads mailing list

jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads_______________________________________________
jakartaee-spec-project-leads mailing list

jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads




_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads__;!!GqivPVa7Brio!LAqjTVQEcglXU5s3uQ1-gMOOlBo4jlJRdxSN2WegAhmeX6fqhlwwJYwfJfRkqKaK7w$





Back to the top