This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new 6c2e4cd1ad git-site-role commit from build_staging.sh
6c2e4cd1ad is described below
commit 6c2e4cd1ad02f2d143cb0b0cab2c5651bc628e74
Author: jenkins <[email protected]>
AuthorDate: Mon Jan 5 12:54:50 2026 +0000
git-site-role commit from build_staging.sh
---
content/bugs/bug_writing_guidelines.html | 61 ++++++++++++++------------------
content/feed.xml | 4 +--
2 files changed, 29 insertions(+), 36 deletions(-)
diff --git a/content/bugs/bug_writing_guidelines.html
b/content/bugs/bug_writing_guidelines.html
index 50fcf35780..6aa94dfdc1 100644
--- a/content/bugs/bug_writing_guidelines.html
+++ b/content/bugs/bug_writing_guidelines.html
@@ -31,19 +31,19 @@
<h4>Why you should read this</h4>
-
-<p> Simply put, the more effectively you report an issue, the more likely an
engineer will actually fix it. These issue writing guidelines are an attempt at
a general tutorial on writing effective issue reports for novice issue writers;
not every sentence may precisely apply to your software project.
-
+<p> Simply put, the more effectively you report an issue, the more likely a
developer will actually fix it.
+ These issue writing guidelines are an attempt at a general tutorial on
writing effective issue reports for novice issue writers;
+ not every sentence may precisely apply to your software project.
<br>
<br>
<h4>How to Write a Useful Issue Report</h4>
<blockquote>
<p>Useful issue reports are ones that get issues fixed. A useful issue report
normally has two qualities:</p></blockquote>
+<ol>
+ <li> <b>Reproducible.</b> If adeveloper can't see it or conclusively prove
that it exists, the engineer will probably stamp it "WORKSFORME" or "INVALID",
and move on to the next issue. Every detail you can provide helps. </li><br><br>
-<ol> <li><b>Reproducible.</b> If an engineer can't see it or conclusively
prove that it exists, the engineer will probably stamp it "WORKSFORME" or
"INVALID", and move on to the next issue. Every detail you can provide helps.
</li><br><br>
-
-<li> <b>Specific.</b> The quicker the engineer can isolate the issue to a
specific problem, the more likely it'll be expediently fixed. <b></b>(If a
programmer or tester has to decipher an issue, they spend more time cursing the
submitter than fixing or testing the problem.) </li> </ol>
+ <li> <b>Specific.</b> The quicker the developer can isolate the issue to a
specific problem, the more likely it'll be expediently fixed. <b></b>(If a
programmer or tester has to decipher an issue, they spend more time cursing the
submitter than fixing or testing the problem.) </li> </ol>
<blockquote> Let's say the application you're testing is a web browser. You
crash at foo.com, and want to write up an issue report: </blockquote>
@@ -53,17 +53,17 @@
<b>Good:</b> "I crashed each time when I opened the attached spreadsheet
document using the 10.13.00 build on a Win NT 4.0 (Service Pack 5) system. I
also rebooted into Linux (RedHat 6.2), and reproduced this problem using the
10.13.00 Linux build.
<p>When I removed the chart from the document I was able to load it without
any trouble." </blockquote>
<br>
-<h4>How to enter a useful Issue Report into IssueZilla</h4>
-<blockquote> In order to file an Issue, you must be a registered user of
OpenOffice.org. Registering is easy: simply click on the "Join" link in the
left navbar and follow the instructions. It takes all of a few minutes. If you
are a registered user, click on the "My Issues" link in the left navbar or on
the <a href="//project_issues.html" target="_blank">"Bugs and Issues"</a> link
on the navbar. The latter is a more comprehensive page which provides a
explanation of IssueZilla and also [...]
-<p> Go to the <a href="//issues/query.cgi" target="_blank">IssueZilla Query
Page</a> to determine whether the defect you've discovered is a known issue and
has already been reported. (If your issue is the 37th duplicate of a known
issue, you're more likely to annoy the engineer. Annoyed engineers fix fewer
issues.)
+<h4>How to enter a useful Issue Report into Bugzilla</h4>
+<blockquote> In order to file an Issue, you must be a registered user of
Apache OpenOffice. Registering is easy: simply click on the "Join" link in the
left navbar and follow the instructions. It takes all of a few minutes. If you
are a registered user, click on the "My Issues" link in the left navbar or on
the <a href="//project_issues.html" target="_blank">"Bugs and Issues"</a> link
on the navbar. The latter is a more comprehensive page which provides a
explanation of IssueZilla and al [...]
+<p> Go to the <a href="https://bz.apache.org/ooo/enter_bug.cgi";
target="_blank">Bugzilla Query Page</a> to determine whether the defect you've
discovered is a known issue and has already been reported. (If your issue is
the 37th duplicate of a known issue, you're more likely to annoy the engineer.
Annoyed developers fix fewer issues.)
-<p>Next, be sure that you've reproduced your issue using a recent build.
(Engineers tend to be most interested in problems afflicting the code base that
they're actively working on, rather than those in a code base that's hundreds
of issue fixes obsolete.)<br> <br> If you've discovered a new issue using a
current build, report it in IssueZilla: </blockquote>
+<p>Next, be sure that you've reproduced your issue using a recent build.
(Developers tend to be most interested in problems afflicting the code base
that they're actively working on, rather than those in a code base that's
hundreds of issue fixes obsolete.)<br> <br> If you've discovered a new issue
using a current build, report it in Bugzilla: </blockquote>
-<ol> <li> <p>From your IssueZilla main page, choose "Enter a new issue".</p>
</li>
+<ol> <li> <p>From your Bugzilla main page, choose "Enter a new issue".</p>
</li>
<li> <p>Select the product that you've found an issue in.</p> </li>
-<li> <p>Enter your E-mail address, Password, and press the "Login" button. (If
you don't yet have a password, leave the password text box empty, and press the
"E-mail me a password" button instead. You'll receive an E-mail message with
your password shortly.)</p> </li> </ol>
+<li> <p>Enter your E-mail address, Password, and press the "Login" button. (If
you don't yet have a password, leave the password text box empty, and press the
"E-mail me a password" button instead. You'll shortly receive an E-mail message
with your password.)</p> </li> </ol>
<h4>Now, fill out the form. Here's what it all means:</h4>
@@ -72,9 +72,9 @@
<blockquote> <b>Product: In which product did you find the issue?</b><br> You
just filled this out on the last page. </blockquote>
<blockquote> <b>Version: In which product version did you first find the
issue?</b><br>
- If applicable. </blockquote>
+ If applicable.</blockquote>
-<blockquote> <b>Component: In which component does the issue exist?</b><br>
IssueZilla requires that you select a component to enter an issue. (If they all
look meaningless, click on the Component link, which links to descriptions of
each component, to help you make the best choice.) </blockquote>
+<blockquote> <b>Component: In which component does the issue exist?</b><br>
Bugzilla requires that you select a component to enter an issue. (If they all
look meaningless, click on the Component link, which links to descriptions of
each component, to help you make the best choice.) </blockquote>
<blockquote> <b>Platform: On which hardware platform did you find this
issue? </b>(e.g., Sun, PC)</><br> If you know the issue happens on all hardware
platforms, choose 'All'. Otherwise, select the platform that you found the
issue on, or "Other" if your platform isn't listed. </blockquote>
@@ -88,11 +88,11 @@
<blockquote > <br><i> Who will be following up on the issue?</i> </blockquote>
-<blockquote> <b>Assigned To: Which engineer should be responsible for fixing
this issue?</b><br> IssueZilla will automatically assign the issue to a default
engineer upon submitting an issue report; the text box exists to allow you to
manually assign it to a different engineer. (To see the list of default
engineers for each component, click on the Component link.) </blockquote>
+<blockquote> <b>Assigned To: Which developer should be responsible for fixing
this issue?</b><br> Bugzilla will automatically assign the issue to a default
developer upon submitting an issue report; the text box exists to allow you to
manually assign it to a different engineer. (To see the list of default
developers for each component, click on the Component link.) </blockquote>
<blockquote> <b>Cc: Who else should receive e-mail updates on changes to this
issue?</b><br> List the full e-mail addresses of other individuals who should
receive an e-mail update upon every change to the issue report. You can enter
as many e-mail addresses as you'd like; e-mail addresses must be separated by
commas, with no spaces between the addresses. </blockquote>
-<blockquote> <br> <i>What else can you tell the engineer about the issue?
</i></blockquote>
+<blockquote> <br> <i>What else can you tell the developer about the issue?
</i></blockquote>
<blockquote> <b>URL: On what URL did you discover this issue?</b><br> If you
encountered the issue on a particular URL, please provide it (or, them) here.
</blockquote>
@@ -108,31 +108,24 @@
<li> <blockquote> <b>Unix:</b> please provide a minimized stack trace.
</blockquote> </li> </ul>
<p><strong>Attachments.</strong><em> </em>
-It may be the
- case you need to add an attachment(s) to an Issue, either the one you file
- or another one. You can do it; the limit is 10MB, but please keep any
attachment
- small, as there are still some using
- 56K
- connections.
- Attaching
- a file to an issue is a two-step procedure and is not obvious. You must
first
- submit the issue or locate the issue to which you wish to attach the file.
- Then, you can add the file as an attachment to that issue. There will be a
link
- in the issue body that reads:
+It may be the case you need to add an attachment(s) to an Issue, either the
one you file
+or another one. You can do it; the limit is 10MB, but please keep any
attachment
+small, as there are still some using 56K connections.
+Attaching a file to an issue is a two-step procedure and is not obvious. You
must first
+submit the issue or locate the issue to which you wish to attach the file.
+ Then, you can add the file as an attachment to that issue. There will be a
link in the issue body that reads:
<blockquote> Create a new attachment (proposed patch, testcase,
etc.)</blockquote>
<p> <strong>Hints</strong>: Reduce the size of your file as much as possible.
And, if you are
- uploading an HTML document, be sure to compress it first (Zip or tar it),
- otherwise it
- may get corrupted when others try to download it.
- <p><strong>MIME types</strong>: Select the correct mime type for you
attachment from the MIME type
- pulldown panel For OpenOffice.org 2.x documents, choose the corresponding
- "application/vnd.oasis.opendocument."
+uploading an HTML document, be sure to compress it first (Zip or tar it),
otherwise it
+may get corrupted when others try to download it.
+<p><strong>MIME types</strong>: Select the correct mime type for you
attachment from the MIME type
+pulldown panel For Apache OpenOffice documents, choose the corresponding
"application/vnd.oasis.opendocument."
<p>You're done!
After double-checking your entries for any possible errors, press the
"Commit" button,
and your issue report will now be in the IssueZilla database.<br>
<hr>
-<p>(These Bug Writing Guidelines were originally written for Mozilla by <a
href= "mailto:[email protected]";><b>Eli Goldberg</b></a>. Thanks to
Claudius Gayle, Peter Mock, Chris Pratt, Louis Suarez-Potts, Tom Schutter,
Rainer Bielefeld, and Chris Yeh for contributing to this document. Constructive
<a href="mailto:[email protected]"; >suggestions and feedback</a>
are welcome.)
+<p>(These Bug Writing Guidelines were originally written for Mozilla by <a
href= "mailto:[email protected]";><b>Eli Goldberg</b></a>. Thanks to
Claudius Gayle, Peter Mock, Chris Pratt, Louis Suarez-Potts, Tom Schutter,
Rainer Bielefeld, and Chris Yeh for contributing to this document. Constructive
<a href="mailto:[email protected]"; >suggestions and feedback</a> are
welcome.)
</blockquote>
</div>
diff --git a/content/feed.xml b/content/feed.xml
index c1f17280d7..382a2f4704 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -6,8 +6,8 @@
<atom:link href="http://localhost:8820/feed.xml"; rel="self"
type="application/rss+xml" />
<description>OpenOffice.org Feed</description>
<language>en-us</language>
- <pubDate>Sun, 4 Jan 2026 14:43:50 +0000</pubDate>
- <lastBuildDate>Sun, 4 Jan 2026 14:43:50 +0000</lastBuildDate>
+ <pubDate>Mon, 5 Jan 2026 12:52:13 +0000</pubDate>
+ <lastBuildDate>Mon, 5 Jan 2026 12:52:13 +0000</lastBuildDate>
</channel>
