Bug 1097126
| Summary: | Known issues from 6.2.0 Release Notes not documented in 6.3.0 Release notes | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Nikoleta Hlavickova <nziakova> |
| Component: | Documentation | Assignee: | Scott Mumford <smumford> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikoleta Hlavickova <nziakova> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.2, 6.2.3, 6.2.4 | CC: | jdoyle, nziakova, rdickens, rsvoboda, smumford, twells |
| Target Milestone: | ER3 | ||
| Target Release: | EAP 6.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-28 15:29:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1051640 | ||
|
Description
Nikoleta Hlavickova
2014-05-13 08:10:06 UTC
Since the documentation workflow for release notes is largely automated, the best way to include these bugs in the 6.3.0 document is to clone them and set the target for this release. Will this cause undue chaos with the development team? Or do clones already exist for these issues? I found clones linked for 980246 [1049276] and 917683 [1072343] but neither of those clones has a target release set, so I'm unsure if pointing them at 6.3.0 will break someone's methodology. I believe that the BZ search on which the Release Notes are based should NOT have specified a target release in its search criteria. To test this theory I have created a second BugDash "dashboard" [1]. [1] https://presentations.cloud.lab.eng.bne.redhat.com/release_note_docs/16 I'm not sure that's a viable approach. We'd be expending resources trying to sort the wheat from the stale chaff (older, irrelevant tickets). Verified in revision 6.3.0-6 |