]
Max Rydahl Andersen commented on JBIDE-18846:
---------------------------------------------
I don't grok what overhead you refer to for the
building/pushing-to-master/review/push-to-production if this only needs updating once a
year.
As I read it you'll need a table for each release for 20-30+ repositories and we got
most of release data available in the website already.
I'm fine you go with adoc if you dont want to put it on the website but you'll be
the one having to make sure it gets updated regularly then and kept in sync.
having it on the website we could have tests for it being correct/working.
create replacement page for cascade/swimlanes pages, to facilitate
access to build, discovery, TP, and update site URLs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-18846
URL:
https://issues.jboss.org/browse/JBIDE-18846
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build, website
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.3.0.Beta1
Borrowing heavily from
https://projects.eclipse.org/list-of-projects we need a new
landing page for the aggregates, which list where to find such things as:
builds (nightly, staging, dev, stable)
updates (nightly, staging, dev, stable)
Jenkins jobs
discovery sites (nightly, staging, dev, stable)
target platforms
etc.
And for each component, we can list:
build
update
Jenkins job
etc.
The old cascade pages are here:
http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html
Unsure whether generated HTML (via script) or simple .adoc is better for this.