-
-- Test the problem at least twice, with source updated a few days apart.
-
- Do not report source tree compilation problems, unless they persist.
+
Current version problem reports.
+
+
+- Test the problem at least twice, with source updated a few days apart.
+
- Do not report source tree compilation problems, unless they persist.
They are almost always your mistake or they are being worked on
as you encounter them. People working on the project are
- doing make build at least once per day, and usually several times
+ doing make build at least once per day, and usually several times
per day with different architectures.
-
- Remember that the anoncvs
+
- Remember that the anoncvs
servers are updated significantly behind the actual working source tree.
-
- Check for changes
- made between OpenBSD versions to see if the problem has been
+
- Check for changes
+ made between OpenBSD versions to see if the problem has been
addressed.
-
- Much care is made in creating snapshots. Sometimes mistakes are made,
+
- Much care is made in creating snapshots. Sometimes mistakes are made,
and our apologies are extended. Reading/writing the e-mail lists
is more appropriate than sending in a bug report.
-
-
-
-Sending in bug reports.
-
+
+
+
+Sending in bug reports.
+
Try to pin-point the exact problem. Never give vague instructions,
or detail vague problems like "it crashes" or "I get strange interrupt
@@ -64,25 +67,26 @@
forums to make sure that someone else is not working on the problem
(saving duplication of effort).
-
+
New features are accepted, especially with code that implements
your suggested new feature.
If someone else writes code for your new feature, the chances are that
it will be misunderstood and created so that you will not recognize it.
-
+
Please remember that projects resources are limited.
-Donations accepted.
+Donations accepted.
-
+
Types of bug reports in order of desirability:
-
-- Repeatable problems with source fixes are the best.
-
- Repeatable problems that are not specific to your hardware/software
+
+- Repeatable problems with source fixes are the best.
+
- Repeatable problems that are not specific to your hardware/software
layout.
-
- Repeatable problems specific to your software layout.
-
- Repeatable problems specific to your hardware layout.
-
- Non-repeatable problems -- or problems you do not wish to repeat.
+
- Repeatable problems specific to your software layout.
+
- Repeatable problems specific to your hardware layout.
+
- Non-repeatable problems -- or problems you do not wish to repeat.
+
@@ -90,6 +94,6 @@
-
-
-
+
+
+
Current version problem reports.
+
+
+- Test the problem at least twice, with source updated a few days apart.
+
- Do not report source tree compilation problems, unless they persist.
They are almost always your mistake or they are being worked on
as you encounter them. People working on the project are
- doing make build at least once per day, and usually several times
+ doing make build at least once per day, and usually several times
per day with different architectures.
-
- Remember that the anoncvs
+
- Remember that the anoncvs
servers are updated significantly behind the actual working source tree.
-
- Check for changes
- made between OpenBSD versions to see if the problem has been
+
- Check for changes
+ made between OpenBSD versions to see if the problem has been
addressed.
-
- Much care is made in creating snapshots. Sometimes mistakes are made,
+
- Much care is made in creating snapshots. Sometimes mistakes are made,
and our apologies are extended. Reading/writing the e-mail lists
is more appropriate than sending in a bug report.
-
-
-
-Sending in bug reports.
-
+
-
+
- Test the problem at least twice, with source updated a few days apart. +
- Do not report source tree compilation problems, unless they persist. They are almost always your mistake or they are being worked on as you encounter them. People working on the project are - doing make build at least once per day, and usually several times + doing make build at least once per day, and usually several times per day with different architectures. -
- Remember that the anoncvs +
- Remember that the anoncvs servers are updated significantly behind the actual working source tree. -
- Check for changes - made between OpenBSD versions to see if the problem has been +
- Check for changes + made between OpenBSD versions to see if the problem has been addressed. -
- Much care is made in creating snapshots. Sometimes mistakes are made, +
- Much care is made in creating snapshots. Sometimes mistakes are made, and our apologies are extended. Reading/writing the e-mail lists is more appropriate than sending in a bug report. -
- -
Sending in bug reports.
-
+
Try to pin-point the exact problem. Never give vague instructions, or detail vague problems like "it crashes" or "I get strange interrupt @@ -64,25 +67,26 @@ forums to make sure that someone else is not working on the problem (saving duplication of effort). -
-
+
- Repeatable problems with source fixes are the best. +
- Repeatable problems that are not specific to your hardware/software layout. -
- Repeatable problems specific to your software layout. -
- Repeatable problems specific to your hardware layout. -
- Non-repeatable problems -- or problems you do not wish to repeat. +
- Repeatable problems specific to your software layout. +
- Repeatable problems specific to your hardware layout. +
- Non-repeatable problems -- or problems you do not wish to repeat. +
@@ -90,6 +94,6 @@