[openmeetings] branch master updated: no jira: security instructions are updated

[so...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

solomax pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openmeetings.git


The following commit(s) were added to refs/heads/master by this push:
     new c46e4b1  no jira: security instructions are updated
c46e4b1 is described below

commit c46e4b1c0e3792718d9b99f0b9442e0d8a16b284
Author: Maxim Solodovnik <so...@gmail.com>
AuthorDate: Thu Mar 1 19:22:11 2018 +0700

    no jira: security instructions are updated
---
 openmeetings-server/src/site/xdoc/security.xml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/openmeetings-server/src/site/xdoc/security.xml b/openmeetings-server/src/site/xdoc/security.xml
index be6fae8..dddf2c4 100644
--- a/openmeetings-server/src/site/xdoc/security.xml
+++ b/openmeetings-server/src/site/xdoc/security.xml
@@ -31,6 +31,12 @@
 				<br/>
 				<a href="https://www.apache.org/security/committers.html#vulnerability-handling">Vulnerability handling guide</a>
 			</p>
+			<p>
+				REFERENCES -> permalink to the announce email in archives<br/>
+				Going forward, please include the product and version information in the description itself 
+				as well as in the "[PRODUCT]" and "[VERSION]" lines in your submissions. 
+				While this may seem redundant, including the information in both places satisfies different use cases and supports automation.
+			</p>
 		</section>
 		<section name="Reporting New Security Problems">
 			<p>

-- 
To stop receiving notification emails like this one, please contact
solomax@apache.org.