[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-340) Review: All to review Beta1 Release Notes

Review: All to review Beta1 Release Notes ----------------------------------------- Key: TOOLSDOC-340 URL: https://issues.jboss.org/browse/TOOLSDOC-340 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Components: Release Notes Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Michelle Murray Fix For: 4.1.0 Attachments: Red_Hat_JBoss_Developer_Studio-7.0-Release_Notes_7.0.0-en-US.pdf *Please review* the Beta1 Release Notes document: 1) Are new features correctly documented? 2) Are there any new features that are missing? 3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301 *Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... *To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway. Just for info: *Note sure if the JIRA needs a release note?* A JIRA needs a release note if: a) the JIRA was reported by GSS b) the JIRA was reported or commented on by a potential user (so someone outside of Red Hat) d) the JIRA fixes a bug that users would have encountered or been aware of c) the JIRA fix may surprise users (in a good or bad way) e) the JIRA documents a bug in a third-party product that impacts the ability to fix JBDS (e.g. pushed patch to Eclipse & waiting on Eclipse release) A JIRA does not need a release note if: a) the JIRA fixes a bug that occurred from an internal build b) the JIRA fixes a bug that users would not have been aware of c) the JIRA was just part of a developer's to-do-list