Commit ac3a9a32 authored by Andriy Palamarchuk's avatar Andriy Palamarchuk Committed by Alexandre Julliard

Updated documentation, mostly improving bugs handling. Direct users to

Bugzilla.
parent 3751ff04
For information on how to post a useful bug report, please
read documentation/bugreports.
read documentation/bugs.sgml.
This is intended to be a place where you should look first if
you want to contribute to Wine development.
......@@ -8,7 +8,7 @@ Wine is still alpha software and is very incomplete.
If you want to help Wine project you can:
* visit Bugzilla (http://wine.codeweavers.com/bugzilla/) for
* visit Bugzilla (http://bugs.winehq.com/) for
list of existing bugs. Metabug 406 lists bugs which are
reasonably simple to fix even for someone new to Wine.
Have a look at it and choose subject you are insterested in.
......
......@@ -177,8 +177,6 @@ winedbg correctly according to documentation/debugger.sgml, you will be dropped
into a debugger so that you can investigate and fix the problem.
For more information on how to do this, please read the file
documentation/debugging.sgml.
If you post a bug report, please read the file documentation/bugs.sgml to
see what information is required.
You should backup all your important files that you give Wine access
to, or use a special Wine copy of them, as there have been some cases
......@@ -209,17 +207,18 @@ WWW: A great deal of information about Wine is available from WineHQ at
FAQ: The Wine FAQ is located at http://www.winehq.com/FAQ
HOWTO: The Wine HOWTO (outdated !) is available at
http://www.westfalen.de/witch/wine-HOWTO.txt .
Usenet: You can discuss Wine-related issues and get help
on comp.emulators.ms-windows.wine.
Usenet: The best place to get help or to report bugs is the Usenet newsgroup
comp.emulators.ms-windows.wine. Please read the file
documentation/bugs.sgml to see what information should be included
in a bug report.
Bugs: Report bugs to Wine Bugzilla at http://bugs.winehq.com/.
Please search the bugzilla database to check whether your
problem is already found before posting a bug report. You can
also post bug reports to comp.emulators.ms-windows.wine.
Please read the file documentation/bugs.sgml to see what
information is required.
Please browse old messages on http://groups.google.com/ to check
whether your problem is already fixed before posting a bug report
to the newsgroup.
HOWTO: The Wine HOWTO (outdated !) is available at
http://www.westfalen.de/witch/wine-HOWTO.txt .
IRC: Online help is available at channel #WineHQ on irc.openprojects.net.
......@@ -231,8 +230,8 @@ Mailing lists:
http://www.winehq.com/dev.shtml#ml for more information.
If you add something, or fix a bug, please send a patch (in 'diff -u'
format) to julliard@winehq.com or to the wine-patches@winehq.com
mailing list for inclusion in the next release.
format) to wine-patches@winehq.com list for inclusion in the next
release.
--
Alexandre Julliard
......
......@@ -19,6 +19,10 @@
advanced developers. You can also make a bug report the hard
way -- advanced developers will probably prefer this.
</para>
<para>
With using either approach report the found issues with relevant
<ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink>.
</para>
<sect2>
<title>The Easy Way</title>
......@@ -49,11 +53,16 @@
</listitem>
<listitem>
<para>
Post a message to the
<systemitem>comp.emulators.ms-windows.wine</systemitem>
newsgroup with the "Nice Formatted Report" attatched. If
possible, upload the full debug output to a web/ftp
server and provide the address in your message.
Post the bug to
<ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink>.
Please, search Bugzilla database to check whether your problem is
already found before posting a bug report.
Include your own detailed description of the problem with
relevant information. Attach the "Nice Formatted Report"
to the submitted bug. Do not cut and paste the report
in the bug description - it is pretty big.
Keep the full debug output in case it will be needed by
Wine developers.
</para>
</listitem>
</orderedlist>
......@@ -88,7 +97,8 @@
<para>Compiler and version (run <command>gcc -v</command>)</para>
</listitem>
<listitem>
<para>Windows version, if installed</para>
<para>Windows version, if used with Wine.
Mention if you don't use Windows</para>
</listitem>
<listitem>
<para>
......@@ -133,6 +143,9 @@
please use <emphasis>only</emphasis> <parameter>+relay</parameter>!! A bug
report with a crash in <parameter>+snoop</parameter>
code is useless in most cases!
You can also turn on other parameters, depending on the nature
of the problem you are researching. See wine man page for full list
of the parameters.
</para>
<para>
To get the trace output, use the following commands:
......@@ -182,12 +195,13 @@
</listitem>
<listitem>
<para>
Post your report to the newsgroup
<systemitem>comp.emulators.ms-windows.wine</systemitem>
Post the bug to
<ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink>.
Please, search Bugzilla database to check whether your problem is
</para>
<para>
In your post, include all of the information from part
1), and insert the text from the output file in part 2).
1), and attach to the bug the output file in part 2).
If you do this, your chances of receiving some sort of
helpful response should be very good.
</para>
......@@ -201,7 +215,7 @@
If after reading this document there is something you
couldn't figure out, or think could be explained better, or
that should have been included, please post to
<systemitem>comp.emulators.ms-windows.wine</systemitem> to
<ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink> to
let us know how this document can be improved.
</para>
</sect2>
......
......@@ -106,7 +106,7 @@ winspool, wnet, x11 and x11drv.
.PP
For more information on debugging messages, see the file
.I documentation/debug-msgs
.I documentation/running.sgml
in the source distribution (FIXME: outdated).
.RE
.TP
......@@ -313,7 +313,7 @@ Please add entries to this list for applications you currently run.
Bug reports and successes may be posted to
.I comp.emulators.ms-windows.wine.
If you want to post a bug report, please read the file
.I documentation/bugreports
.I documentation/bugs.sgml
in the
.B wine
source to see what information is necessary (FIXME: outdated).
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment