From a7e9d3f37d5e9fba4b9acaa43e7c12b6d9a669ae Mon Sep 17 00:00:00 2001 From: Mike Hommey Date: Thu, 8 Jun 2006 10:59:26 +0200 Subject: Load /tmp/libxml2-2.6.26 into libxml2/branches/upstream/current. --- doc/bugs.html | 118 +++++++++++++++++++++++++++++----------------------------- 1 file changed, 59 insertions(+), 59 deletions(-) (limited to 'doc/bugs.html') diff --git a/doc/bugs.html b/doc/bugs.html index 6415c85..c755d00 100644 --- a/doc/bugs.html +++ b/doc/bugs.html @@ -7,62 +7,62 @@ H1 {font-family: Verdana,Arial,Helvetica} H2 {font-family: Verdana,Arial,Helvetica} H3 {font-family: Verdana,Arial,Helvetica} A:link, A:visited, A:active { text-decoration: underline } -Reporting bugs and getting help

The XML C parser and toolkit of Gnome

Reporting bugs and getting help

Main Menu

Related links

Well, bugs or missing features are always possible, and I will make a -point of fixing them in a timely fashion. The best way to report a bug is to -use the Gnome -bug tracking database (make sure to use the "libxml2" module name). I -look at reports there regularly and it's good to have a reminder when a bug -is still open. Be sure to specify that the bug is for the package libxml2.

For small problems you can try to get help on IRC, the #xml channel on -irc.gnome.org (port 6667) usually have a few person subscribed which may help -(but there is no garantee and if a real issue is raised it should go on the -mailing-list for archival).

There is also a mailing-list xml@gnome.org for libxml, with an on-line archive (old). To subscribe to this list, -please visit the associated Web page and -follow the instructions. Do not send code, I won't debug it -(but patches are really appreciated!).

Please note that with the current amount of virus and SPAM, sending mail -to the list without being subscribed won't work. There is *far too many -bounces* (in the order of a thousand a day !) I cannot approve them manually -anymore. If your mail to the list bounced waiting for administrator approval, -it is LOST ! Repost it and fix the problem triggering the error. Also please -note that emails with -a legal warning asking to not copy or redistribute freely the informations -they contain are NOT acceptable for the mailing-list, -such mail will as much as possible be discarded automatically, and are less -likely to be answered if they made it to the list, DO NOT -post to the list from an email address where such legal requirements are -automatically added, get private paying support if you can't share -informations.

Check the following before -posting:

Read the FAQ and use the - search engine to get information related to your problem.
Make sure you are using a recent - version, and that the problem still shows up in a recent version.
Check the list - archives to see if the problem was reported already. In this case - there is probably a fix available, similarly check the registered - open bugs.
Make sure you can reproduce the bug with xmllint or one of the test - programs found in source in the distribution.
Please send the command showing the error as well as the input (as an - attachment)

Then send the bug with associated information to reproduce it to the xml@gnome.org list; if it's really libxml -related I will approve it. Please do not send mail to me directly, it makes -things really hard to track and in some cases I am not the best person to -answer a given question, ask on the list.

To be really clear about support:

Support or help requests MUST be sent to - the list or on bugzilla in case of problems, so that the Question - and Answers can be shared publicly. Failing to do so carries the implicit - message "I want free support but I don't want to share the benefits with - others" and is not welcome. I will automatically Carbon-Copy the - xml@gnome.org mailing list for any technical reply made about libxml2 or - libxslt.
There is no garantee of support, if - your question remains unanswered after a week, repost it, making sure you - gave all the detail needed and the information requested.
Failing to provide information as requested or double checking first - for prior feedback also carries the implicit message "the time of the - library maintainers is less valuable than my time" and might not be - welcome.

Of course, bugs reported with a suggested patch for fixing them will -probably be processed faster than those without.

If you're looking for help, a quick look at the list archive may actually -provide the answer. I usually send source samples when answering libxml2 -usage questions. The auto-generated documentation is -not as polished as I would like (i need to learn more about DocBook), but -it's a good starting point.

Daniel Veillard

+Reporting bugs and getting help

The XML C parser and toolkit of Gnome

Reporting bugs and getting help

Main Menu

Related links

Well, bugs or missing features are always possible, and I will make +apointof fixing them in a timely fashion. The best way to report a bug is +touse theGnomebugtracking +database(make sure to use the "libxml2" module name). Ilook atreports +there regularly and it's good to have a reminder when a bugis stillopen. Be +sure to specify that the bug is for the package libxml2.

For small problems you can try to get help on IRC, the #xml +channelonirc.gnome.org (port 6667) usually have a few person subscribed which +mayhelp(but there is no garantee and if a real issue is raised it should go +onthemailing-list for archival).

There is also a mailing-list xml@gnome.orgfor libxml, with an on-line archive(old). To subscribe to this +list,pleasevisit the associatedWebpage +andfollow the instructions. Do not send code, I won'tdebug +it(but patches are really appreciated!).

Please note that with the current amount of virus and SPAM, sending +mailtothe list without being subscribed won't work. There is *far too +manybounces*(in the order of a thousand a day !) I cannot approve them +manuallyanymore.If your mail to the list bounced waiting for administrator +approval,it isLOST ! Repost it and fix the problem triggering the error. Also +pleasenotethat emails +withalegal warning asking to not copy or redistribute freely the +informationstheycontainare NOTacceptable for the +mailing-list,suchmail will as much as possible be discarded automatically, +and are lesslikelyto be answered if they made it to the list, DO +NOTpost tothe list from an email address where such legal +requirements areautomaticallyadded, get private paying support if you can't +shareinformations.

Check the following beforeposting:

Read the FAQand usethesearch engineto get information related to + your problem.
Make sure you are using + arecentversion, and that the problem still shows up in a + recentversion.
Check the listarchivesto see if + theproblem was reported already. In this casethere is probably a + fixavailable, similarly check the registeredopenbugs.
Make sure you can reproduce the bug with xmllint or one of + thetestprograms found in source in the distribution.
Please send the command showing the error as well as the input + (asanattachment)

Then send the bug with associated information to reproduce it to the xml@gnome.orglist; if it's +reallylibxmlrelated I will approve it. Please do not send mail to me +directly, itmakesthings really hard to track and in some cases I am not the +best persontoanswer a given question, ask on the list.

To be really clear about support:

Support or help requests MUST be senttothe + list or on bugzillain case of problems, so that theQuestionand + Answers can be shared publicly. Failing to do so carries + theimplicitmessage "I want free support but I don't want to share + thebenefits withothers" and is not welcome. I will automatically + Carbon-Copythexml@gnome.org mailing list for any technical reply made + about libxml2orlibxslt.
There is no garantee of + support,ifyour question remains unanswered after a week, repost + it, making sureyougave all the detail needed and the information + requested.
Failing to provide information as requested or double checking + firstforprior feedback also carries the implicit message "the time of + thelibrarymaintainers is less valuable than my time" and might not + bewelcome.

Of course, bugs reported with a suggested patch for fixing +themwillprobably be processed faster than those without.

If you're looking for help, a quick look at the list +archivemayactuallyprovide the answer. I usually send source samples when +answeringlibxml2usage questions. The auto-generateddocumentationisnot +as polished as I would like (i need to learn moreabout DocBook), butit's a +good starting point.

Daniel Veillard

-- cgit v1.2.3