[jbosstools-issues] [JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066631#comment-13066631 ] 

Nick Boldt commented on JBIDE-18846:
------------------------------------

Devdoc is now merged. Spoke with [~rob.stryker] and here's some feedback on the above prototype:

1. Re: *Maturity* column

{quote} i would prefer you use words that have been defined, yes.  So supported / tested / techpreview / exper / ea   is fine  if you link to this document [1]{quote}

[1] https://devstudio.redhat.com/9.0/staging/updates/#central 

2. Re: asciidoc markup or yaml?

{quote}whichever is easier for you to keep updated. assuming both are equally difficult (change text somewhere)  then i prefer asciidoc{quote}

3. Re: flowchart on [2]

[2] http://download.jboss.org/jbosstools/builds/cascade/master.html ( http://download.jboss.org/jbosstools/builds/cascade/images/HowWeBuild_Diagram_Cascade_JBT41.png )

{quote} that image is useless. It's not small enough to be an effective thumbnail, and not large enough to read the text{quote}

So... I'm going to flesh it out and fix the broken links (stuff moved because JBDS-3208 is now done). yaml is a good idea but then I have to go through the overhead of building, pushing to master, reviewing, pushing to production. 

This way we can just stick doc in jbosstools-devdoc. We rarely add a new project and going a glob F&R once a year to update links isn't a huge overhead compared to having to build yaml w/ rake. And there's nothing HTML5'y we need to do here, afaict, so plain ol' adoc should be fine.

> 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)