To be clear, it is not unusual to update the spec document without
updating the API source files, and vice versa.
Also note that versioning of the two artifacts is handled
differently. Spec documents do not get a "micro" version number,
they get a "rev level".
So, you can put them in the same repo, as was previously
recommended, but the version numbers have to be managed
independently, as does publication of the artifacts.
Steve Millidge (Payara) wrote on
10/11/19 6:43 AM:
My
preference is the same repo as is current simply because
they can then be tagged, branched and versioned as a single
repo. However that is not a strong preference.
Steve
From: ee4j-pmc-bounces@xxxxxxxxxxx
<ee4j-pmc-bounces@xxxxxxxxxxx>
On Behalf Of Ivar Grimstad
Sent: 11 October 2019 14:32
To: ee4j-pmc@xxxxxxxxxxx
Subject: [ee4j-pmc] Specification Project
structure...
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
|
