[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-709) JBDS 9.1 GA: Document a use case for Forge Tooling
Supriya Bharadwaj (JIRA)
issues at jboss.org
Fri Feb 5 07:32:00 EST 2016
[ https://issues.jboss.org/browse/TOOLSDOC-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159209#comment-13159209 ]
Supriya Bharadwaj commented on TOOLSDOC-709:
--------------------------------------------
> Tried out steps for the use case; most of the commands at https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Studio/6.0/html/Forge_Reference_Guide/index.html are out dated
> Pinged Vlado to know the QE for Forge (psrna); QE in conference in Brno today
> From the JBDS Cheat Sheets, going through and adding important points to https://docs.google.com/document/d/1uetvmtaQ93jwDmHePRafebGV06Wls8-H7vY4KPdhUYI/edit
> Went through http://forge.jboss.org/document/sample-forge-usage-tasks
> JBDS 9.1 GA: Document a use case for Forge Tooling
> --------------------------------------------------
>
> Key: TOOLSDOC-709
> URL: https://issues.jboss.org/browse/TOOLSDOC-709
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Components: General documentation issues
> Affects Versions: 9.1 GA
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
> Labels: Forge
> Fix For: 9.1 GA
>
>
> Document a use case for Forge tooling.
> 1. Draft a potential use case for what users may want to do with forge.
> 2. Get review on use case idea from a relevant SME or QE person
> 3. Write an intro and flesh out the use case with relevant screenshots
> 4. Get QE review
> 5. Create upstream and downstream versions of approved content.
> a. Add CSP version to customer portal
> b. Send Misha upstream version
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list