This is an automated email from the ASF dual-hosted git repository.
digro pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
The following commit(s) were added to refs/heads/main by this push:
new ca8dd99bf1 Updated issues.html
ca8dd99bf1 is described below
commit ca8dd99bf18205dcc5524e0ad38255233ddc33f2
Author: DiGro <[email protected]>
AuthorDate: Mon Jan 5 13:50:34 2026 +0100
Updated issues.html
Switched IssueZilla to Bugzilla
Switched OpenOffice.org to Apache OpenOffice
---
content/bugs/issues.html | 50 ++++++++++++++++++++++--------------------------
1 file changed, 23 insertions(+), 27 deletions(-)
diff --git a/content/bugs/issues.html b/content/bugs/issues.html
index e0ec5d4bff..7fac482d01 100644
--- a/content/bugs/issues.html
+++ b/content/bugs/issues.html
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<html><head>
-<title>Got Issues? (Last updated 2002-06-03)</title>
+<title>Got Issues? (Last updated 2026-01-05)</title>
<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
</head>
<body>
@@ -9,7 +9,7 @@
<h2>Got Issues?</h2>
-<p><i>Last updated 2002-06-03</i></p>
+<p><i>Last updated 2026-01-05</i></p>
<br>
@@ -27,16 +27,15 @@
possibly help out or offer feedback
</p>
<br>
- <h4>What Is IssueZilla?</h4>
+ <h4>What Is Bugzilla?</h4>
- <p>IssueZilla, a proprietary tool, is based on Mozilla's open-source <a
- href="http://www.mozilla.org/bugs/";>Bugzilla</a>, but has been
+ <p>Bugzilla is Mozilla's open-source <a
href="http://www.mozilla.org/bugs/";>Bugzilla</a>, but has been
generalized by <a href="http://www.collab.net";>CollabNet</a> to handle all
kinds of issues, not just code-based
- issues. On OpenOffice.org, the supported issue-types now include:
+ issues. On Apache OpenOffice, the supported issue-types now include:
DEFECT, ENHANCEMENT, FEATURE, TASK and PATCH. We can add issue types in
the future as necessary, and these can be reported against specific
components of a project, for example 'documentation', 'code', 'ui',
- 'definition'. OpenOffice.org's projects are 'api', 'chart', 'database
+ 'definition'. Apache OpenOffice's projects are 'api', 'chart', 'database
access', 'drawing', 'formula editor', 'presentation', 'spreadsheet',
'word processor' and 'xml' to name just a few. Take a look at the
projects/products list to see all of them.
@@ -47,9 +46,9 @@
<h4>What do you have an issue with?</h4>
<p>Do you want to report an issue with a milestone build or with a copy
- of OpenOffice.org that you compiled yourself? IssueZilla is the place
+ of Apache OpenOffice that you compiled yourself? Bugzilla is the place
to submit issue reports for software distributed by
- OpenOffice.org. This page gives an overview of how IssueZilla works.
+ Apache OpenOffice. This page gives an overview of how Bugzilla works.
Read the <a
href="//bugs/bug_writing_guidelines.html">issue
writing guidelines</a> as well, for tips on how to write useful issue
@@ -66,19 +65,16 @@
<dt><b>Project</b></dt>
<dd>
- OpenOffice.org is composed of different projects. Carefully
- read the <a
- href="/projects/">project
- descriptions</a> if you're unsure of which project to attribute
+ Apache OpenOffice is composed of different projects. Carefully read the
<a
+ href="/projects/">project descriptions</a> if you're unsure of which
project to attribute
your issue to (visit the projects themselves for fuller descriptions).
The project you choose determines which person
- IssueZilla assigns the issue to.
+ Bugzilla assigns the issue to.
</dd>
<dt><b>Status Whiteboard</b></dt>
<dd>
- The Status Whiteboard is used for writing short notes about the
- issue.
+ The Status Whiteboard is used for writing short notes about the issue.
</dd>
<dt><b>Keywords</b></dt>
@@ -92,13 +88,13 @@
</dt>
<dd>
- Developers can post <tt>helpwanted</tt> notices, and IssueZilla can
+ Developers can post <tt>helpwanted</tt> notices, and Bugzilla can
help match-make other developers and apprentices who wish to help
out with a TASK. Developers should Write <tt>helpwanted</tt> in the
Keywords field of an issues, perhaps changing the issue-type of the
defect or enhancement to 'TASK'. Others searching for things to do
will find it and even accept the issue or TASK. People interested
- in getting involved can search IssueZilla for issues and
+ in getting involved can search Bugzilla for issues and
ENHANCEMENTs marked <tt>helpwanted</tt>. Maybe one of them will
have the expertise and resources to help you with your problem.
</dd>
@@ -169,13 +165,13 @@
<h4>Life Cycle Of An Issue</h4>
<p>What happens to an issue when it is first reported depends on who
- reported it. New IssueZilla accounts by default create issues which are
+ reported it. New Bugzilla accounts by default create issues which are
<tt>UNCONFIRMED</tt>.
- Currently, on IssueZilla, the quality assurance is done by
+ Currently, on Bugzilla, the quality assurance is done by
a list of users subscribed to a "virtual user"
issues@<project>.openoffice.org.
<p>
- You then use your regular IssueZilla account to
+ You then use your regular Bugzilla account to
login, then view, then further "workflow" the issue.
<br>
<P><A NAME="emailreply"></A>
@@ -187,12 +183,12 @@
all changes in bugs of this project.
</p>
- <p>If you are a registered OpenOffice.org user, you
+ <p>If you are a registered Apache OpenOffice user, you
can create <tt>UNCONFIRMED</tt> issues.
When an issue is confirmed and becomes <tt>NEW</tt>, the
developer will probably look at the issue and either accept it or give
it to someone else. If the issue remains new and inactive for more than
- a week, IssueZilla nags the issue's owner with email until action is
+ a week, Bugzilla nags the issue's owner with email until action is
taken. Whenever an issue is reassigned or has its component changed,
its status is set back to <tt>NEW</tt>. The <tt>NEW</tt> status means
that the issue is newly added to a particular developer's plate, not
@@ -229,7 +225,7 @@
<dd>
The problem described is not a issue, or not a issue in
- OpenOffice.org.
+ Apache OpenOffice.
</dd>
<dt><b>WONTFIX</b></dt>
@@ -272,10 +268,10 @@
<dt><b>MOVED</b></dt>
<dd>
- The issue was specific to a particular OpenOffice.org-based
- distribution and didn't affect OpenOffice.org code. One such
+ The issue was specific to a particular Apache OpenOffice-based
+ distribution and didn't affect Apache OpenOffice code. One such
scenario are defects reported against Sun's product version of
- OpenOffice.org. The issue was moved to the bug database of the
+ Apache OpenOffice. The issue was moved to the bug database of the
distributor of the affected OpenOffice.org derivative.
</dd>
</dl>
