summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--SUPPORT15
1 files changed, 8 insertions, 7 deletions
diff --git a/SUPPORT b/SUPPORT
index 5d85207..f1705aa 100644
--- a/SUPPORT
+++ b/SUPPORT
@@ -25,7 +25,8 @@ directly.
25 25
26In brief, always provide the version of the software that you are 26In brief, always provide the version of the software that you are
27using, and when requesting features or reporting bugs, first check to 27using, and when requesting features or reporting bugs, first check to
28see that the issue has not already been addressed in the CVS tree. 28see that the issue has not already been addressed in the current Git
29code.
29 30
30GETTING HELP 31GETTING HELP
31 32
@@ -47,8 +48,8 @@ REPORTING BUGS AND SUBMITTING PATCHES
47 48
48Bug reports, investigations of possible bugs, feature requests, and 49Bug reports, investigations of possible bugs, feature requests, and
49patch submissions should be submitted to the development list at 50patch submissions should be submitted to the development list at
50mailto:nagiosplug-devel@lists.sourceforge.net. Please raise a tracker first 51mailto:nagiosplug-devel@lists.sourceforge.net. Please raise an issue first
51in Sourceforge, otherwise your email is likely to be missed over time. 52in GitHub, otherwise your email is likely to be missed over time.
52 53
53You should identify the version, preferably in the subject line. 54You should identify the version, preferably in the subject line.
54However, to best use developer resources, it is suggested that you 55However, to best use developer resources, it is suggested that you
@@ -56,10 +57,10 @@ reference your report to one of the following sources:
56 57
57 1) The most recent release, including beta's 58 1) The most recent release, including beta's
58 59
59 2) The twice-daily snapshots (there's a link provided on 60 2) The current snapshots (there's a link provided on
60 http://nagiosplug.sourceforge.net) 61 https://www.nagios-plugins.org/download.html)
61 62
62 3) The current CVS tree from sourceforge 63 3) The current Git code from GitHub
63 64
64(This does not mean you should run any of these sources in a 65(This does not mean you should run any of these sources in a
65production environment - the latter two you clearly should 66production environment - the latter two you clearly should
@@ -69,7 +70,7 @@ which are most recent.)
69 70
70From experience, I know that most bugs can be fixed with only a few 71From experience, I know that most bugs can be fixed with only a few
71more moments work than it takes to determine if the bug is still 72more moments work than it takes to determine if the bug is still
72present in the CVS tree. If you can save a developer the expense of 73present in the Git tree. If you can save a developer the expense of
73that time, you ensure that bugs are fixed more rapidly, and thus you 74that time, you ensure that bugs are fixed more rapidly, and thus you
74ensure your problem resolution is reflected in a stable release more 75ensure your problem resolution is reflected in a stable release more
75quickly. 76quickly.