Hi, Jeongkyu Kim wrote:
I had a chance to install Solaris 10 x86 several days ago. Actually, ILoveSolaris10 promotion by Sun Korea (http://www.ilovesolaris10.co.kr) worked for me :-) Except that I had to install 3rd party network and sound card driver, everything has been smooth. JDS looks neat and it also has StarOffice 7. As OO.o community contributor, next step was installing OO.o. While I was playing with it, I found several glitches and filed the issues.
- no application icons in JDS http://www.openoffice.org/issues/show_bug.cgi?id=49522 - StarSuite menus launches OO.o after installing OO.ohttp://www.openoffice.org/issues/show_bug.cgi?id=49527
However, the answer was almost same as 'no support for OO.o on Solaris'. I understand that Solaris is not pouplar platform for OO.o users. But, I still have several questions on that. - The comment says "StarOffice 8 will be integrated in JDS. No need for an OpenOffice.org version.". If it is true then why OO.o project distributes Solaris version? Is it only for Solaris without JDS?
That appears to be the primary target. Older versions of Solaris prior to Solaris 10 or upcoming OpenSolaris don't include StarOffice or (all of) JDS. In that case you won't have conflicts between OOo and SO/JDS desktop integration.
Another case is installing and testing OOo prerelease builds. You may want to do this even on a JDS system. But in that case you might elect to not install the desktop integration package for OOo to avoid such conflicts.
- Also, another comment says "This means taht we, the SUN part of the community won't fix this. If someone else in the community is willing to fix this he should reopen this issue. Keeping all issues open that might be fixed by someone somewhere in the future will only lead to an enormous backlog of issues. <Won't fix> doesn't mean that this issue never ever will be touched again. ". Regarding to this comment, I understand that resources are limited to supoort every trivial issue on every platform. But, I don't agree that 'an enormous backlog of issues' is bad. It is natural consequence of supporting varety of platforms/languages. In addition to that, if Issuezilla is not Sun's bug database, why Sun has to close the issues just because they won't fix it?
I believe closing the issue as WONTFIX for the cited reason is indeed wrong. The correct approach would be to keep the issue open with target milestone 'OOo Please Help'.
But such an issue still fills up the bug 'inbox' of the assigned owner. Maybe we need an accepted way to 'park' such issues elsewhere. IMHO the qa project should think about this problem - and more generally provide clear guidelines how to deal with such issues and make developers aware of them.
And, I believe that meaning of 'won't fix' is really 'won't fix'. The documentation explains that 'WONTFIX: The problem described is an issue which will never be fixed'. ( http://www.openoffice.org/scdocs/issue_lifecycle.html ) How do you guys think?
Yes. I think WONTFIX should be reserved for issues that don't fit the strategy and roadmap of the project or should not be in the general OOo version for technical reasons, i.e a conscious decision that even a contributed patch would not be accepted.
Ciao, J�rg -- Joerg Barfurth Sun Microsystems - Desktop - Hamburg >>>>>>>>>>>>>>>>>> using std::disclaimer <<<<<<<<<<<<<<<<<<<<<<< Software Engineer [EMAIL PROTECTED] OpenOffice.org Configuration http://util.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
