[jakartaee-spec-project-leads] Merging EE4J_8 branch into Jakarta EE 8 b

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jakartaee-spec-project-leads] Merging EE4J_8 branch into Jakarta EE 8 branch (master)

From: arjan tijms <arjan.tijms@xxxxxxxxx>
Date: Sat, 13 Jul 2019 01:45:32 +0200
Delivered-to: jakartaee-spec-project-leads@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jakartaee-spec-project-leads>
List-help: <mailto:jakartaee-spec-project-leads-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads>, <mailto:jakartaee-spec-project-leads-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jakartaee-spec-project-leads>, <mailto:jakartaee-spec-project-leads-request@eclipse.org?subject=unsubscribe>

Hi,

After a quick glance at some repos it looks like not every project has merged the EE4J_8 branch into the branch in which it is preparing the Jakarta EE 8 release (which is typically master).

Maybe individual projects have good reasons for this, but maybe some projects just forgot this.

Might be good to check explicitly for each project that no changes made in the EE4J_8 branch unintentionally get left out for the Jakarta EE 8 release?

Kind regards,

ARJAN

Follow-Ups:
- Re: [jakartaee-spec-project-leads] Merging EE4J_8 branch into Jakarta EE 8 branch (master)
  - From: Dmitry Kornilov

Prev by Date: [jakartaee-spec-project-leads] GAVs should not be updated for Jakarta EE 8
Next by Date: Re: [jakartaee-spec-project-leads] Merging EE4J_8 branch into Jakarta EE 8 branch (master)
Previous by thread: [jakartaee-spec-project-leads] GAVs should not be updated for Jakarta EE 8
Next by thread: Re: [jakartaee-spec-project-leads] Merging EE4J_8 branch into Jakarta EE 8 branch (master)
Index(es):
- Date
- Thread

Breadcrumbs