https://issues.apache.org/ooo/show_bug.cgi?id=122300

            Bug ID: 122300
        Issue Type: DEFECT
           Summary: Update the README file
    Classification: Code
           Product: General
           Version: AOO400-dev
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: P3
         Component: code
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]

The README file needs to be updated in several aspects. Some examples:

"For latest updates to this readme file, see
http://www.openoffice.org/welcome/readme.html";

This page has "OpenOffice.org 3.0 ReadMe"

"The Apache OpenOffice Community, responsible for the development of this
product, would like to invite you to participate as a community member. As a
new user, you can check out the OpenOffice site with helpful user information
at http://www.openoffice.org/about_us/introduction.html";

This page is outdated, from 2007, even if it redirects, it should be removed
from the README or updated to reflect new content


Remove the "System Requirements" from the "Notes on Installation" completely,
or simply point to the version on the user portal (Note: in this case, create a
general page that redirects to the actual one, for example
http://www.openoffice.org/sysreqs/lates.html --->
http://www.openoffice.org/sysreqs/400.html)


"Extension Database Incompatibility", if I understood clearly, talks about a
change in the Berkeley db on 3.2, this is also outdated even for 3.4, where
this db was completely replaced.


Check if SESSION_MANAGER tip in "Problems During Program Startup" is still
valid on Gnome.


Check if "File Locking" is still valid.


In "User Support", update link to user forums, and check other links

In "How to Start", the linl is obsolete.


"Subscribe" has still old incubator mail addresses.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Reply via email to