[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-pmc] Specification Project structure...
|
Thanks, Scott. And,
as long as it's just a recommendation and not a requirement, then I think
we're good.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutterFrom:
Scott
Stark <starksm64@xxxxxxxxx>To:
EE4J
PMC Discussions <ee4j-pmc@xxxxxxxxxxx>Date:
10/11/2019
09:03 AMSubject:
[EXTERNAL]
Re: [ee4j-pmc] Specification Project structure...Sent
by: ee4j-pmc-bounces@xxxxxxxxxxx
The spec committee came up with the recommendation to
leave the api and spec together:https://github.com/jakartaee/specification-committee/blob/master/operations.adoc#recommended-specification-project-repository-structureOn Fri, Oct 11, 2019 at 8:32 AM Ivar
Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
wrote:Hi,Do we as PMC have an opinion on whether
to recommend the spec projects to split the spec documents and api sources
in separate git repos or have them in the same?Should we provide some guidelines? Or
leave it to the projects to decide?Ivar-- Ivar
Grimstad
Jakarta
EE Developer Advocate | Eclipse
Foundation, Inc.
Eclipse
Foundation:
The Platform for Open Innovation and Collaboration_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc