Re: New year cleaning up database unconfirmed issues party

Christoph Lukasiak <[email protected]>
Newsgroups gmane.comp.openoffice.dba.devel,gmane.comp.openoffice.questions
Message-ID <[email protected]>
sorry, wrong link:

Christoph Lukasiak wrote:
> moin database testing folks,
>
> i would like to start a 'new year cleaning up db unconfirmed issues' 
> week (or two) to reduce this issues maybe under 50 (~120 last week, 
> under 100 at the moment, after diligent work mainly from drew, as i 
> know), not let any issues untouched and to check if they are still 
> valid (specially the older ones) .. so please support the OOo QA Base 
> team with this work and let us keep our area clean and up-to-date.
>
>
> p.s. also newbies are welcome to help
>
> we use following query: 
> https://sunspace.sfbay.sun.com/display/SOUX/2010-02-23
naturally we use this one: 
http://qa.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&component=Database+access&issue_status=UNCONFIRMED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=%27Importance%27
> further info about issue handling you get here: 
> http://qa.openoffice.org/ooQAReloaded/ooQA-IssueRules.html
> please have following rules in mind: 
> http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-BasicRules.html
>
>
> bye chris
> (http://wiki.services.openoffice.org/wiki/User:Clu)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.