Summary: | Help: Workbench under the covers - Enhancement | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Daniel U. Thibault <d.u.thibault> |
Component: | Doc | Assignee: | Platform-Doc-Inbox <platform-doc-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | d.u.thibault |
Version: | 3.5 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Daniel U. Thibault
2009-09-15 13:18:24 EDT
> Is there a better way of submitting fixes to the doc?
You're welcome to enter a single bug with a number of fixes together, but please at least enter separate bugs for each top level doc book as these pieces all have different maintainers (platform user guide, plugin developer guide, Java development guide, etc).
You can also checkout the doc from CVS. Paste this connection into the CVS REpository view:
:pserver:dev.eclipse.org:/cvsroot/eclipse
Username: "anonymous", leave password blank. Then you can checkout the doc plugins from HEAD (org.eclipse.platform.doc.* and org.eclipse.jdt.doc.*). Make the desired changes, then select "Create Patch" on individual projects in the "Synchronize" view. Attach the patch to a bug and you're done.
This might ultimately be simpler for you because it avoids explaining where the change is (second sentence of third paragraph of section w/x/y in book z, etc).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |