no jira: instructions updated according to board comments
Project: http://git-wip-us.apache.org/repos/asf/openmeetings/repo Commit: http://git-wip-us.apache.org/repos/asf/openmeetings/commit/c8b1afb3 Tree: http://git-wip-us.apache.org/repos/asf/openmeetings/tree/c8b1afb3 Diff: http://git-wip-us.apache.org/repos/asf/openmeetings/diff/c8b1afb3 Branch: refs/heads/3.2.x Commit: c8b1afb3b0faf15f6d63a2eaf5c3a192d3229f25 Parents: f639443 Author: Maxim Solodovnik <[email protected]> Authored: Thu Apr 20 01:40:00 2017 +0000 Committer: Maxim Solodovnik <[email protected]> Committed: Thu Apr 20 01:40:00 2017 +0000 ---------------------------------------------------------------------- openmeetings-server/src/site/xdoc/ReleaseGuide.xml | 4 ---- 1 file changed, 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/openmeetings/blob/c8b1afb3/openmeetings-server/src/site/xdoc/ReleaseGuide.xml ---------------------------------------------------------------------- diff --git a/openmeetings-server/src/site/xdoc/ReleaseGuide.xml b/openmeetings-server/src/site/xdoc/ReleaseGuide.xml index 4015a08..b1227ec 100644 --- a/openmeetings-server/src/site/xdoc/ReleaseGuide.xml +++ b/openmeetings-server/src/site/xdoc/ReleaseGuide.xml @@ -187,16 +187,12 @@ mvn deploy -Pdeploy,rc <a href="http://mail-archives.apache.org/mod_mbox/openmeetings-dev/201701.mbox/%3CCAJmbs8jZ7EiXoeBbG4ynvg30FPx2nAOJMypE2Qp-v-c63ayO9A%40mail.gmail.com%3E";>example Vote email</a> <a href="http://s.apache.org/vote-2.0.0RC4";>example Vote email (Incubator)</a> <br /> - Forward (Not CC) this Vote email to: [email protected]<br /> - <br /> After the vote is over, send a "RESULT" email to the list with the subject line:<br /> [RESULT][VOTE] Apache OpenMeetings x.xx release<br /> An example for such an email: <a href="http://mail-archives.apache.org/mod_mbox/openmeetings-dev/201701.mbox/%3CCAJmbs8gyvHuarzdVma%2BF6ap7RHBhhVciZp5Oi5JogQdLR6o0NA%40mail.gmail.com%3E";>example Result email</a> <br /> - Forward (Not CC) this RESULT VOTE email to: [email protected]<br /> - <br /> Votes on whether a package is ready to be released use majority approval -- i.e., at least three PMC members must vote affirmatively for release, and there must be more positive than negative votes. Releases may not be vetoed. Before voting +1 PMC members
