[libreoffice-users] Re: Suggestions to PTB

In news:4E558B12.1030205@nouenoff.nl,
Cor Nouws <oolst@nouenoff.nl> typed:
> Hi Twayne,
>
> Twayne wrote (24-08-11 21:44)
> > Can we expect there to be a "stop" any time soon in
> > development in order to attack and destroy some of the
> >     bugs and problems? Along with that, a bug list of
> > what's being fixed, in process and and fixed would go a
> > long, long ways. I always read the change lists, but
> > they don't do a whole lot of good when I'm not familian
> > with that bug, often because the description is
> > different than the accepted bug description.
>
> Bugzilla and all other info is public.
> It is relatively easy to query for bugs, fixed,
> enhancements etc.
> A great page, with many queries predefined, is this one:
> http://wiki.documentfoundation.org/BugReport_Details
>
> Other useful info for your help:
> http://wiki.documentfoundation.org/BugTriage
> http://wiki.documentfoundation.org/BugReport
> http://wiki.documentfoundation.org/QA
>
> If you do that yourself, the developers have their hands
> free to continue fixing bugs, improving build, helping
> other devs etc. :-)
> HTH,
>
> --
>   - Cor
>   - http://nl.libreoffice.org

Being "Publc" has no bearing on this. Digging out the data I mentioned is a 
huge job and sometimes impossible unless you're involved with the problem 
itself. For instance, the image problems in a huge file; half the 
entries/variations of the issue are not there. And many others. Maybe you 
can sit there for hours making sure something isn't already reported, but I 
won't do that. The tool just is not userfrendly for the types of information 
displayed in the manner it needs to be displayed in.
    I take it your last sentence indicates I should do the fixes myself? No, 
I can't do that. I doubt I would anyway, considering how hard it is to find 
all of the complaints at once and get a nice, clean output to work to.

But back to my original comment: I think some of the more serious bugs need 
a concerted effort to be fixed, especially in largish files with over x 
images on this page, y image on those pages, and so forth.
   Also, when something is meant to apply to LO, it should NOT have titles, 
headers about OOo that keeps popping up.
   Also, when you install a new version, the only place you see the full 
version is under Help About. All the way thru the install process, it only 
says "3" or "3.3", not 3.3.4 and so on. It's always been like that AFAIK. 
Once started, you don't know whether you downloaded the right package or not 
since it's a 3-digit rev and only one or two digits of the rev are given. I 
call stuff like that "dirty" and needing to be swept or the caked mud 
removed.

You're looking at a tree, not the forest. If the forest doesn't have the 
right trees speces, there may be little to be harvested from it, which is my 
case. I would simply like to see what's beng worked on clearly listed out, 
along wth what's not planned, etc., as it is now but with an easier way to 
bring all related bugs into one list.
   I would love to tell MS to kiss my shiny metal butt, but I can't as long 
as some of these serious bugs continue to be ignored. One man can push one 
car; as you're doing now, but not three or four at the same time. All this 
is part of watching out for the future of LO and being able to say its users 
are solidly behind it. Anythng that doesn't work shouldn't have been 
released until it does work.

HTH,

Twayne`




-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted