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 c926ccc git-site-role commit from build_staging.sh
c926ccc is described below
commit c926cccaba4dba667aa6506156beadf2c9dd40d8
Author: jenkins <[email protected]>
AuthorDate: Mon Mar 22 14:36:19 2021 +0000
git-site-role commit from build_staging.sh
---
content/feed.xml | 4 ++--
.../qa/issue_handling/bug_writing_guidelines.html | 24 +++++++++++-----------
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/content/feed.xml b/content/feed.xml
index 577f0b0..2241fd9 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>Mon, 22 Mar 2021 14:29:07 +0000</pubDate>
- <lastBuildDate>Mon, 22 Mar 2021 14:29:07 +0000</lastBuildDate>
+ <pubDate>Mon, 22 Mar 2021 14:35:04 +0000</pubDate>
+ <lastBuildDate>Mon, 22 Mar 2021 14:35:04 +0000</lastBuildDate>
</channel>
diff --git a/content/qa/issue_handling/bug_writing_guidelines.html
b/content/qa/issue_handling/bug_writing_guidelines.html
index e43ae1c..fa958fd 100644
--- a/content/qa/issue_handling/bug_writing_guidelines.html
+++ b/content/qa/issue_handling/bug_writing_guidelines.html
@@ -30,13 +30,13 @@
<h4>Consider the rules<br>
</h4>
<p>We strongly encourage you to read the <a href="basic_rules.html">Basic
-IssueTracker rules</a> - for those who work with IssueTracker on a
+Bugzilla rules</a> - for those who work with Bugzilla on a
day-by-day base, they have proven to <span style="font-style:
italic;">immensely</span>
reduce their work. It's really easy for you to report issues in a way
which cost all others a lot of time, but if you invest a little more
effort in the beginning, you save others a lot thereof afterwards.<br>
</p>
-<p>Thus, if you're new to OpenOffice.org's IssueTracker, please <a
+<p>Thus, if you're new to OpenOffice's Bugzilla, please <a
href="basic_rules.html"> read the rules</a>. And, of course, please
follow them :-), to make our all work easier, so we can concentrate on
improving the product, instead of wasting time with bad issue reports.</p>
@@ -77,7 +77,7 @@ 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." </p>
</blockquote>
-<h4>How to enter a useful Issue Report into IssueTracker</h4>
+<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 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
@@ -86,8 +86,8 @@ 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 IssueTracker and also has some
useful IssueTracker links, such as a query link.
- <p> Go to the <a href="http://www.openoffice.org/issues/query.cgi";
- target="_blank">IssueTracker Query Page</a> to determine whether the
+ <p> Go to the <a href="https://bz.apache.org/ooo/query.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 engineers fix fewer issues.)
@@ -101,14 +101,14 @@ If you've discovered a new issue using a current build,
report it in
IssueTracker: </p>
<ol>
<li> If you're not already logged in, please enter your username
-& password in the appropriate filds at the top of this page (or any
+& password in the appropriate fields at the top of this page (or any
other page on this site)</li>
- <li> From your IssueTracker main page, choose "Enter a new issue".</li>
+ <li> From your Bugzilla main page, choose "Enter a new issue".</li>
<li> Select the product that you've found an issue in.</li>
</ol>
<p>regarding 2., there is a link "File Issue" as well, accessible
from the "My Pages"-tab (When logging in you're automatically directed
-to "My Pages", you can then access IssueTracker using the links in the
+to "My Pages", you can then access Bugzilla using the links in the
"My Tools" box on the left side of your screen)</p>
</blockquote>
<h4>Now, fill out the form. Here's what it all means:</h4>
@@ -208,7 +208,7 @@ 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: </p>
<blockquote> Create a new attachment (proposed patch, testcase,
etc.)</blockquote>
- <p> <strong>Note</strong>: You cannot add OpenOffice.org files
+ <p> <strong>Note</strong>: You cannot add OpenOffice files
natively. They must be added as "binary" files. This is a temporary
problem. </p>
<p> Hints: Reduce the size of your file as much as possible. And, if
@@ -217,16 +217,16 @@ or tar it), otherwise it gets corrupted when others try
to download it.
</p>
<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 IssueTracker database.<br>
+the Bugzilla database.<br>
</p>
<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, and Chris Yeh for contributing to this document.
-Constructive suggestions and feedback is welcome. In this case just
+Constructive suggestions and feedback are welcome. In this case just
post your suggestions to the <a
- href="mailto:[email protected]?subject=IssueTracker";>dev@qa</a>
+ href="mailto:[email protected]?subject=Bugzilla";>dev@qa</a>
mailing list.) </p>
</blockquote>
</div>
