@@ -16,6 +16,11 @@ Please keep the following issues in mind when submitting a bug/issue:
1616 Security/vulnerability reports should not be submitted through GitHub, but instead
1717 please send your report to the email address:
1818 `mapserver-security nospam @ osgeo.org` (remove the blanks and 'nospam').
19+
20+ .. tip::
21+
22+ Review MapServer's `Security Policy <https://github.com/MapServer/MapServer/blob/main/SECURITY.md/>`__,
23+ and also review any recent published `vulnerabilities <https://github.com/MapServer/MapServer/security/advisories?state=published/>`__.
1924
20251. Set a meaningful yet reasonably brief title of your ticket.
2126
@@ -36,15 +41,15 @@ Please keep the following issues in mind when submitting a bug/issue:
3641
3742The most important thing when reporting a bug is to boil down a minimum
3843example that is needed to reproduce the bug. That means a minimal mapfile +
39- any data files it depends on. Remove everything from the map file that isn't
44+ any data files it depends on. Remove everything from the mapfile that isn't
4045needed to reproduce the bug.
4146
4247The developers often dislike having to spend the first 30 minutes working on a
4348bug, having to fix paths, remove unnecessary layers, removing references to
4449external symbols or fonts that were not included or even needed and otherwise
4550doctoring your test case to get it to a point when they can actually use it.
4651
47- If the bug is easily demonstrated with " :ref:`map2img`" , without the need to
52+ If the bug is easily demonstrated with :ref:`map2img`, without the need to
4853setup a proper web service and test it through http, then please show it that
4954way. If a standalone :ref:`mapscript` script can demonstrate a problem without it
5055having to be a web service, likewise submit it that way. If your problem
0 commit comments