[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-spec-project-leads] Merging of EE4J_8 branches?
|
You should delete the EE4J_8 branch after it is merged with master.
Tom Jenkinson wrote on 3/4/20 6:47 AM:
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?
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://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads__;!!GqivPVa7Brio!ITvT2GwJGSYp_oScioJOkVAwCufW9TFEFHVE4MXrZWkXUcWfmeHDdiisnBTiVIXcsw$