Apache OpenOffice (AOO) Bugzilla – Issue 11477
URGENT: need access to http://www.openoffice.org/issues/bug_status.html
Last modified: 2003-12-27 10:23:17 UTC
We would like to specify the Priority description in http://www.openoffice.org/issues/bug_status.html#priority in more details. How do we get access to the document. I can find it in CVS, I assume this document is tight to the IssueZilla installation. Can you please provide a location of this document or the document itself, so that we can create a patch.
Martin: If you write the changes you want, then attach the file, I can submit them to the instantiation engineers who will make the necessary changes and put them on the server. Thanks
Created attachment 4762 [details] New priority definitions as announced on the qa and releases list
Created attachment 4768 [details] New priority definitions as announced on the releases and qa list (HTML)
I attached both a plain text and a HTML document with the new priority definitions. It's a bit more text than usual at http://www.openoffice.org/issues/bug_status.html#priority but it's important to have it there.
Louis, Stefan and Martin- Could you review Michael's attachment and determine if it meets with your expectations?
I was unable to read the 'HTML' version but the text version content seemed okay and more functionally descriptive than the current version. I think it is okay. -louis
Created attachment 4793 [details] New working zipped html version of priority definitions
Attached a new zipped HTML version, which doesn't work again. I declared it to be an HTML attachment, that seems to be the reason. I wanted to call it type "other", but IZ didn't accept ZIP as a mime type. How am I supposed to attach HTML files? But I guess we don't need it anyways, the text file should be good enough.
note- confirmed w/ MH on our call this morning using the text file as mentioned Action Plan- 1) submit file to engineering to replace other issue priority description 2) update this issue when that change has been made pcn 15180 filed, step 1 complete timeframe: I will update this issue by 2/21
the file has been changed on the server, please test and verify
Hi Kenneth, looks perfect, thanks.Set it to "resolved fixed" in the first step.
Verified and closed.