Re: [jakarta.ee-spec.committee] Issue with dependencies

[Scott Stark <sstark@xxxxxxxxxx>]

Right but what I’m talking about is a view of the current staging status for a given release. So right now, Arjan wanted to do a staging release of Jakarta Authorization, but this has a dependency on Jakarta Servlets which is not staged. Once we are in the process of a release, there needs to be a way to determine if all dependencies of a given spec project have been staged.

On Jul 15, 2019, at 1:38 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

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.