We already have a bunch of dependency information:
https://github.com/eclipse-ee4j/jakartaee-platform/blob/master/namespace/dependencies.adoc
https://github.com/eclipse-ee4j/ee4j-website/blob/master/src/dot/dependencies.dot
https://github.com/eclipse-ee4j/ee4j-website/blob/master/src/dot/relationships.dot
https://github.com/eclipse-ee4j/ee4j-website/blob/master/src/dot/specs.dot
https://www.eclipse.org/ee4j/specs.php
Scott Stark wrote on 7/15/19 12:04 PM:
That does bring up the question of how future releases should be
handled. This time around we have a lot of bootstrapping and
getting TCK jobs at the individual spec project is one, so I see
the benefit in doing the release in two steps.
In the future, it would seem that we should have a
dependency graph of the projects for a given release that shows
the various nodes as either green/red so that a project knows if
its dependencies have been staged by lookin at the graph status.
Could be a jobs we run from the spec committee Jenkins and push
to a location under the jakarta.ee specifications subtree.
Yes,
unfortunately,
that's the state we're in. If the TCK runs do not have
the "final"
staging repository dependencies, then they will have to
be re-run... This
whole Jakarta EE 8 release is kind of funky in that
regard.
---------------------------------------------------
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/kevinwsutter
From:
Scott
Stark <sstark@xxxxxxxxxx>
To:
Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:
07/15/2019
10:03 AM
Subject:
[EXTERNAL]
[jakarta.ee-spec.committee] Issue with dependencies
Sent
by: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx
In a
discussion with Arjan and Dmitry
today about the TCK jobs, it came up that specs have
dependencies that
are not available in staging as yet, so they cannot
really do the final
staging release. I guess that is why we have the
schedule broken up into
a phase where individual specs pass the TCK without
updating dependencies
in their pom, and once all specs have done that and
are staged, the “Make
API staging releases” step entails restating API jars
with updated dependencies
in their pom files?
Are we expecting that the TCK jobs are re-run and the
release review PRs
updated?
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
