Mercurial > web-octave
changeset 279:54532ba03391
Redirect and merge /bugs to /support page.
* pages/bugs.md: make redirect to /support.
* pages/menu/support.md: merge content of pages/menu/bugs.md.
* pages/menu/bugs.md: delete page.
author | Kai T. Ohlhus <k.ohlhus@gmail.com> |
---|---|
date | Sun, 08 May 2022 02:29:31 +0900 |
parents | a24a65b3001b |
children | 2bf083b44c5c |
files | _layouts/redirect.html pages/bugs.md pages/menu/bugs.md pages/menu/support.md |
diffstat | 4 files changed, 91 insertions(+), 77 deletions(-) [+] |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/_layouts/redirect.html Sun May 08 02:29:31 2022 +0900 @@ -0,0 +1,13 @@ +<!DOCTYPE html> +<html lang="en"> +<head> + <link rel="canonical" href="{{ page.redirect_to | relative_url }}"> + <meta http-equiv="content-type" content="text/html; charset=utf-8"> + <meta http-equiv="refresh" content="0; url={{ page.redirect_to | relative_url }}"> + <title>Redirecting...</title> +</head> +<body> + <h1>Redirecting...</h1> + <a href="{{ page.redirect_to | relative_url }}">Click here if you are not redirected.</a> +</body> +</html>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/pages/bugs.md Sun May 08 02:29:31 2022 +0900 @@ -0,0 +1,8 @@ +--- +layout: redirect +sitemap: false +permalink: bugs +redirect_to: support +--- + +<!-- Redirect old permalink since 2022-05-08 -->
--- a/pages/menu/bugs.md Sat May 07 23:14:24 2022 +0900 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,77 +0,0 @@ ---- -layout: page -title: Bugs -icon: <i class="fas fa-bug"></i> -menu: true -permalink: bugs ---- - -GNU Octave uses the bug tracker at [GNU Savannah]({{ site.bugs_url }}). -There you can -[<i class="far fa-plus-square"></i> report a new bug](https://savannah.gnu.org/bugs/?group=octave&func=additem), -[<i class="far fa-list-alt"></i> browse recent bugs]({{ site.bugs_url }}), -or [<i class="fas fa-search"></i> search for bugs](https://savannah.gnu.org/bugs/?group=octave&func=search). - -### Guidelines for reporting a new bug - -<a href="{{ "/img/savannah_bug_report.png" | relative_url }}"> - <img src="{{ "/img/savannah_bug_report.png" | relative_url }}" - style="max-height: 250px; width: auto;" alt="Savannah bug report"> -</a> - -1. **Is the bug already known?** - - [<i class="fas fa-search"></i> Search for already reported bugs](https://savannah.gnu.org/bugs/?group=octave&func=search) - at the bug tracker first. - If you your problem **does not appear** to be known, - then you should report the problem. - -2. **Is it really a bug?** - - - If Octave **crashes**, for any input whatever, that is a bug. - Reliable interpreters never crash. - - If Octave produces **incorrect results**, for any input whatever, - that is a bug. - - If Octave produces an **error message** for **valid input**, that is a bug. - - If Octave produces **no error message** for **invalid input**, - that is a bug. - - <p></p> - -3. **Missing function in Octave** - - If a function exists in Matlab, but not in Octave, this is **not** a bug. - - - The function might already be - [part of an Octave package]({{ site.sourceforge_url }}/functions_by_alpha.php). - - You may file a **feature request** for it on the bug tracker. - - <p></p> - - Please be aware that it might take **several months** - until for new features become part of Octave. - Consider [<i class="fas fa-comment-dollar"></i> commercial support]({{ "commercial-support.html" | relative_url }}) - if you don't want to wait that long. - -4. **Make your bug report count** - - - **Report all the facts:**<br> - Include all information that make it possible to fix the bug. - If you are not sure whether to state a fact or leave it out, state it. - This information includes your **operating system**, **Octave version**, - **exact error message** or **exact output**. - - **Give a short, specific, complete example:**<br> - Avoid: pseudocode, uninitialized variables, - calls to unattached scripts or functions. - - **Justify your expectations briefly:**<br> - Although it might seem obvious to you, - someone examining the problem might not know what result you consider - correct. - - -### Sending Patches for Octave - -If you have a suggested fix for a bug, -please attach it to your report in the tracker. -Your patch is more likely to be reviewed if you follow the guidelines from the -Octave Wiki about the [creation of changesets]({{ site.wiki_url }}/Mercurial).
--- a/pages/menu/support.md Sat May 07 23:14:24 2022 +0900 +++ b/pages/menu/support.md Sun May 08 02:29:31 2022 +0900 @@ -46,3 +46,73 @@ - Setup assistance - Custom feature implementation </div> + +#### <i class="fas fa-bug"></i> Report a bug + +GNU Octave uses the bug tracker at [GNU Savannah]({{ site.bugs_url }}). +There you can +[<i class="far fa-plus-square"></i> report a new bug](https://savannah.gnu.org/bugs/?group=octave&func=additem), +[<i class="far fa-list-alt"></i> browse recent bugs]({{ site.bugs_url }}), +or [<i class="fas fa-search"></i> search for bugs](https://savannah.gnu.org/bugs/?group=octave&func=search). + +<a href="{{ "/img/savannah_bug_report.png" | relative_url }}"> + <img src="{{ "/img/savannah_bug_report.png" | relative_url }}" + style="max-height: 250px; width: auto;" alt="Savannah bug report"> +</a> + +1. **Is the bug already known?** + + [<i class="fas fa-search"></i> Search for already reported bugs](https://savannah.gnu.org/bugs/?group=octave&func=search) + at the bug tracker first. + If you your problem **does not appear** to be known, + then you should report the problem. + +2. **Is it really a bug?** + + - If Octave **crashes**, for any input whatever, that is a bug. + Reliable interpreters never crash. + - If Octave produces **incorrect results**, for any input whatever, + that is a bug. + - If Octave produces an **error message** for **valid input**, that is a bug. + - If Octave produces **no error message** for **invalid input**, + that is a bug. + + <p></p> + +3. **Missing function in Octave** + + If a function exists in Matlab, but not in Octave, this is **not** a bug. + + - The function might already be + [part of an Octave package]({{ site.sourceforge_url }}/functions_by_alpha.php). + - You may file a **feature request** for it on the bug tracker. + + <p></p> + + Please be aware that it might take **several months** + until for new features become part of Octave. + Consider [<i class="fas fa-comment-dollar"></i> commercial support]({{ "commercial-support.html" | relative_url }}) + if you don't want to wait that long. + +4. **Make your bug report count** + + - **Report all the facts:**<br> + Include all information that make it possible to fix the bug. + If you are not sure whether to state a fact or leave it out, state it. + This information includes your **operating system**, **Octave version**, + **exact error message** or **exact output**. + - **Give a short, specific, complete example:**<br> + Avoid: pseudocode, uninitialized variables, + calls to unattached scripts or functions. + - **Justify your expectations briefly:**<br> + Although it might seem obvious to you, + someone examining the problem might not know what result you consider + correct. + + +#### Sending Patches for Octave + +If you have a suggested fix for a bug, +please attach it to your report in the tracker. +Your patch is more likely to be reviewed if you follow the guidelines from the +Octave Wiki about the [creation of changesets]({{ site.wiki_url }}/Mercurial).