[jbosstools-issues] [JBoss JIRA] (JBDS-4461) Document list of features, versions, and quality status of devstudio 11 contents

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBDS-4461 at 7/19/17 2:57 PM:
-----------------------------------------------------------

{quote}Is there a way to make the output a little less computer and a little more human readable? {quote} Yes, someone could write a parsing script to strip out dupe/undesired info. 

{quote}If we could massage the data to strip some of the information and present it in easier to read/sort, it might work.{quote} We could parse the data into CSV so it could then be imported to a Google Doc spreadsheet. Then you can sort/format to your heart's content. :D

{quote}It also doesn't state quality of the version{quote} True, but everything is GA at this point unless it's explicitly called out as pre-GA tech preview (in the RTD) or it's available from RH Central after enabling Early Access.

{quote}higher level of stating only components{quote} True, you get 4 features for Openshift rather than just one line item; for Fuse there are 5 features. So it's a bit more granular than just a "here are the 17 projects in jbosstools" list, like if you look at https://github.com/jbosstools or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-buildflow_master/configure-readonly/ 

{quote}who is going to scan that 1k line document{quote} Well that's the $1k question. Who actually WANTS this document, and what level of detail do they need? This feels like an exercise in "hot potato" crossed with "if we build it, *maybe* they will come?" :D


was (Author: nickboldt):
{quote}
Is there a way to make the output a little less computer and a little more human readable? {quote} Yes, someone could write a parsing script to strip out dupe/undesired info. 

{quote}If we could massage the data to strip some of the information and present it in easier to read/sort, it might work.{quote} We could parse the data into CSV so it could then be imported to a Google Doc spreadsheet. Then you can sort/format to your heart's content. :D

{quote}It also doesn't state quality of the version{quote} True, but everything is GA at this point unless it's explicitly called out as pre-GA tech preview (in the RTD) or it's available from RH Central after enabling Early Access.

{quote}higher level of stating only components{quote} True, you get 4 features for Openshift rather than just one line item; for Fuse there are 5 features. So it's a bit more granular than just a "here are the 17 projects in jbosstools" list, like if you look at https://github.com/jbosstools or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-buildflow_master/configure-readonly/ 

{quote}who is going to scan that 1k line document{quote} Well that's the $1k question. Who actually WANTS this document, and what level of detail do they need? This feels like an exercise in "hot potato" crossed with "if we build it, *maybe* they will come?" :D

> Document list of features, versions, and quality status of devstudio 11 contents
> --------------------------------------------------------------------------------
>
>                 Key: JBDS-4461
>                 URL: https://issues.jboss.org/browse/JBDS-4461
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 11.0.0.AM2
>            Reporter: Nick Boldt
>            Assignee: Jeff MAURY
>             Fix For: 11.0.0.GA
>
>         Attachments: whats-in-devstudio-features-plugins-only.txt, whats-in-devstudio.png, whats-in-devstudio.txt
>
>
> We need an updated document that details the list of all the stuff that's in devstudio 11.
> This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-rhuqRuwVLQ4/edit#gid=0 but needs to be a fresh document as much of the content has changed, upversioned or been removed. 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)