To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=61685
                  Issue #:|61685
                  Summary:|provide a means to remove all easter eggs from
                          |release versions
                Component:|Spreadsheet
                  Version:|OOo 2.0
                 Platform:|Macintosh
                      URL:|
               OS/Version:|All
                   Status:|UNCONFIRMED
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|configuration
              Assigned to:|spreadsheet
              Reported by:|larsnooden





------- Additional comments from [EMAIL PROTECTED] Mon Feb  6 06:45:30 -0800 
2006 -------
Provide a means to remove all the eastereggs from release versions.  

Just saying to remove the offending bits from the source code and recompile
it, is not an appropriate solution for the *end users or sysadmins*.  

It is perfectly reasonable to expect that a defect be addressed as part of the
development team.  

Making it possible for an admin to block all Easter Eggs would be a quick fix. 

If it is such an important issue to retain the eggs, and the only option you are
willing to entertain is that the end users or sysadmins to maintain their own
fork, then provide instructions on how to do so.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to