This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/plc4x-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new dafdb68 Site checkin for project PLC4X: Jenkins Tools
dafdb68 is described below
commit dafdb689af1e382579fd27f7cd161e08ab405aba
Author: jenkins <[email protected]>
AuthorDate: Tue Feb 18 12:08:30 2020 +0000
Site checkin for project PLC4X: Jenkins Tools
---
developers/release/release.html | 54 ++++++++++++++++++++---------------------
1 file changed, 27 insertions(+), 27 deletions(-)
diff --git a/developers/release/release.html b/developers/release/release.html
index 1152e1e..c2c8347 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -772,36 +772,36 @@ The following would be the one used to do our first TLP
release:</p>
</div>
<div class="listingblock">
<div class="content">
-<pre> E-Mail Topic:
- [VOTE] Apache PLC4X 0.7.0 RC1
+<pre>E-Mail Topic:
+[VOTE] Apache PLC4X 0.7.0 RC1
- Message:
- Apache PLC4X 0.7.0 has been staged under [2] and it’s time to vote
- on accepting it for release. All Maven artifacts are available under [1].
- Voting will be open for 72hr.
+Message:
+Apache PLC4X 0.7.0 has been staged under [2] and it’s time to vote
+on accepting it for release. All Maven artifacts are available under [1].
+Voting will be open for 72hr.
- A minimum of 3 binding +1 votes and more binding +1 than binding -1
- are required to pass.
+A minimum of 3 binding +1 votes and more binding +1 than binding -1
+are required to pass.
- Release tag: release/0.7.0
- Hash for the release tag: {replacethiswiththerealgitcommittag}
+Release tag: release/0.7.0
+Hash for the release tag: {replacethiswiththerealgitcommittag}
- Per [3] "Before voting +1 PMC members are required to download
- the signed source code package, compile it as provided, and test
- the resulting executable on their own platform, along with also
- verifying that the package meets the requirements of the ASF policy
- on releases."
+Per [3] "Before voting +1 PMC members are required to download
+the signed source code package, compile it as provided, and test
+the resulting executable on their own platform, along with also
+verifying that the package meets the requirements of the ASF policy
+on releases."
- You can achieve the above by following [4].
+You can achieve the above by following [4].
- [ ] +1 accept (indicate what you validated - e.g. performed the non-RM
items in [4])
- [ ] -1 reject (explanation required)
+[ ] +1 accept (indicate what you validated - e.g. performed the non-RM items
in [4])
+[ ] -1 reject (explanation required)
- [1]
https://repository.apache.org/content/repositories/orgapacheplc4x-{somefourdigitnumber}
- [2] https://dist.apache.org/repos/dist/dev/plc4x/0.7.0/rc1
- [3] https://www.apache.org/dev/release.html#approving-a-release
- [4]
https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release</pre>
+[1]
https://repository.apache.org/content/repositories/orgapacheplc4x-{somefourdigitnumber}
+[2] https://dist.apache.org/repos/dist/dev/plc4x/0.7.0/rc1
+[3] https://www.apache.org/dev/release.html#approving-a-release
+[4]
https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release</pre>
</div>
</div>
<div class="paragraph">
@@ -834,13 +834,13 @@ The following would be the one used to do our first TLP
release:</p>
</div>
<div class="listingblock">
<div class="content">
-<pre> E-Mail Topic:
- [RESULT] [VOTE] Apache PLC4X 0.7.0 RC1
+<pre>E-Mail Topic:
+[RESULT] [VOTE] Apache PLC4X 0.7.0 RC1
- Message:
- So, the vote passes with 3 +1 votes by PMC members and one +1 vote by a
non PMC member.
+Message:
+So, the vote passes with 3 +1 votes by PMC members and one +1 vote by a non
PMC member.
- Chris</pre>
+{Release Manager Name}</pre>
</div>
</div>
</div>