Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | two different build documents on the website | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Unknown <non-migrated> |
Component: | Documentation | Assignee: | lsuarezpotts |
Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | issues@www <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, nesshof |
Version: | current | ||
Target Milestone: | --- | ||
Hardware: | Sun | ||
OS: | Solaris | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Unknown
2000-12-06 10:23:17 UTC
Reassigned to louis for ownership (to coordinate support from chris toward resolution) Please verify this has been resolved, then close issue. If not, then considering legacy related issue experience / responsibility / ownership may more appropriately be reassigned to goolie (to coordinate support from chris toward resolution). The issue seems to be that the second, competing version of the build documentation below (tools.openoffice.org), is apparently incorrect. I can notify the owner of the page that his document seems to be in error and may have to be updated. -L I'm a bit confused... Unfortunately I still see two different versions of the build document. I also can't find the source of the build document under tools.openoffice.org when I check out www. But most of all, I don't understand why we have two versions. I'm often updating/correcting the build docs (www/www/dev_docs/source/ build.html) and don't see why we should create two copies of the same file. armin Martin, Armin has pointed out that there are two different build documents on the website, and that this causes some confusion. In the interest of eliminating confusion, we should, if possible, use only one build document for users, whichever is the correct one. Armin seems to indicate that the one in /dev_docs/is the correct one.... -Louis have notified the project leader of the situation closing issue for lack of interest. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. |