Bugzilla – Full Text Bug Listing
| Summary: | Move TPTP docs to DITA | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Nellie Chau <nelliec> |
| Component: | TPTP | Assignee: | Ruth Lee <ruthdaly> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | dtprice |
| Version: | unspecified | Keywords: | Documentation |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | closed460 | ||
|
Description
Nellie Chau
*** Bug 74825 has been marked as a duplicate of this bug. *** This feature has been brought forward to the planning group to be moved to a future release. This has been deferred to 4.1. Deferring from 4.1 as per the official 4.1 enhancement plan. http://eclipse.org/tptp/home/project_info/featureplans/features.php?source=All&project=All&release=4.1&file=TPTPFeatures_4.1.xml This enhancement should be reconsidered. Moving topics to DITA will require resource to change existing docs to XML DITA format. It will also increase the complexity and resource required to produce docs by adding a "transform" step. Also, I have yet to see a project at IBM where we have cashed in on the promised benefits of XML DITA. I believe that getting value out of XML DITA will require additional resource investment. Given the resource crunch, this does not seem viable. I would put my resource into improving the content rather than moving to a new source format that will have little user benenfit. Let some of the larger projects go to XML DITA first. When they have proven the customer value, then reconsider. Today, the doc model we have (working directly in HTML) is simple, efficient and suited to our situation of limited doc resource. I agree that the doc tracking & consistency problems that we've discussed have higher priority. No plans to move to DITA in the short term. If a product has a requirement for this, then the product should open a new bugzilla for that requirement and explain why it's needed in the bugzilla. Won't be considered unless a consuming product needs this feature. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |