[
https://issues.jboss.org/browse/TOOLSDOC-388?page=com.atlassian.jira.plug...
]
Nick Boldt commented on TOOLSDOC-388:
-------------------------------------
I've already made changes in the 4.1.x/7.1.x branch so that references within JBDS to
its update site (located at
https://devstudio.jboss.com/updates/7.0/ ) refer to it as the
7.x site, not the 7.0 or 7.1 site. That way I won't have to update it again from 7.1
to 7.[whatever is decided*] later, when we do a maintenance release to pick up Kepler
SR2.
You might want to consider updating docs similarly to "7.x" so that you too
won't need to change explicit refs in docs to "7.1" to "7.1.1" or
"7.2" in 6 months when Kepler SR2 is out.
Update explicit 7.0 text references in docs to 7.1
--------------------------------------------------
Key: TOOLSDOC-388
URL:
https://issues.jboss.org/browse/TOOLSDOC-388
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Components: General documentation issues
Affects Versions: 4.1.0
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.1.1
Original Estimate: 5 hours, 30 minutes
Time Spent: 55 minutes
Remaining Estimate: 1 hour, 30 minutes
Section that need updating
*Installation Guide*
* 2.2. Supported Operating Systems and Architectures
* 2.3. Computer Memory
* 2.4. Compatible Java Developer Kits
* 3.2. Install JBoss Developer Studio
* 3.3. Install JBoss Developer Studio BYOE
* 5.2. Upgrade JBoss Developer Studio
* 5.3. Upgrade JBoss Developer Studio BYOE
* B.1. Build the Universal Installer from Source
*Migration Guide* (2.2 and 2.3 shared with Installation Guide)
* 2.2. Upgrade JBoss Developer Studio
* 2.3. Upgrade JBoss Developer Studio BYOE
* 3.1. Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
*Getting Started Guide* (3.2 shared with Installation Guide)
* 2.1. About Getting Started
* 3.1. Installation Assumptions
* 3.2. Install JBoss Developer Studio
* 4.3. Tutorial Assumptions
*User Guide*
* None
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira