The release process (RM Guide) involves generating several emails for discussion and voting.
Samples of those emails are included below. Note the "To:" and "Subject:" in addition to the content.
See https://reference.apache.org/committer/email for info on how to send email as your @apache.org address.
NOTE: if you copy paste a sample's "code block" directly into your mail composition window you may see oddities with respect to fonts. Copying the code block to a simple editor window first (e.g., an emacs buffer) and then copying from there seems to yield better results.
Dev LAST CALL email
To: dev@edgent.apache.org Subject: [LAST CALL] Apache Edgent 1.2.0-incubating release This is the last call prior to proceeding with the release. Reply to this by [one-week] if there is any reason to defer proceeding such as features/fixes/RELEASE_NOTES, etc not yet complete. This includes lobbying for open JIRAs that you believe should be addressed. Apache Edgent release process documentation: [1] and [2]. [3] is tracking the release checklist items and their status. [1] https://cwiki.apache.org/confluence/display/EDGENT/A+guide+to+the+Apache+Edgent+release+process [2] https://cwiki.apache.org/confluence/display/EDGENT/Release+Manager's+Guide [3] https://issues.apache.org/jira/browse/EDGENT-277
Dev DISCUSS email [create thread]
To: dev@edgent.apache.org Subject: [DISCUSS] Apache Edgent 1.2.0-incubating release Use this thread to discuss any issues that arise during the release process. The develop branch is frozen and should contain all of the content required for the release. If you believe this not to be the case please respond. You are not yet required to perform any validation of the release. The RM will verify the Jenkins build and test results [4] and will proceed accordingly. The thread will be updated with release branch and tag and RC information once they are created. I’m soliciting contributors to help out and take ownership of sub-tasks in [3] that haven’t yet been assigned. Those items involving external things like the website and blogging have to wait until the release is approved and made available but please accept the items now. Thanks in advance! Apache Edgent release process documentation: [1] and [2]. [3] is tracking the release checklist items and their status. [1] https://cwiki.apache.org/confluence/display/EDGENT/A+guide+to+the+Apache+Edgent+release+process [2] https://cwiki.apache.org/confluence/display/EDGENT/Release+Manager's+Guide [3] https://issues.apache.org/jira/browse/EDGENT-277 [4] https://builds.apache.org/view/E-G/view/Edgent/
Dev DISCUSS email [update thread]
Reply to the [DISCUSS] thread...
Release branch master:release/1.2 has been created.
The tag edgent-1.2.0 marks the release candidate's contents.
Jenkins should be building and testing the branch [1].
The develop branch is open for future development.
The RC is staged in [2] and [3].
You are not yet required to perform any validation of the release.
[1] https://builds.apache.org/view/E-G/view/Edgent/
[2] https://dist.apache.org/repos/dist/dev/incubator/edgent/
[3] https://repository.apache.org/#stagingRepositories (log in with your Apache userId/pw)
or https://repository.apache.org/content/repositories/orgapacheedgent-XXXX
dev@ RC VOTE
To: dev@edgent.apache.org
Subject: [VOTE] Apache Edgent 1.2.0-incubating-RC1
1.2.0-incubating/rc1 has been staged under [3] and [4] and it’s time
to vote on accepting it for release. If approved we will seek final
release approval from the IPMC.
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.
Per [5] "Before voting +1 [P]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 [6].
[ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [6])
[ ] -1 reject (explanation required)
Apache Edgent release process documentation: [1] and [2].
[1] https://cwiki.apache.org/confluence/display/EDGENT/A+guide+to+the+Apache+Edgent+release+process
[2] https://cwiki.apache.org/confluence/display/EDGENT/Release+Manager's+Guide
[3] https://dist.apache.org/repos/dist/dev/incubator/edgent/
[4] https://repository.apache.org/#stagingRepositories (log in with your Apache userId/pw)
or https://repository.apache.org/content/repositories/orgapacheedgent-XXXX
[5] https://www.apache.org/dev/release.html#approving-a-release
[6] https://cwiki.apache.org/confluence/display/EDGENT/Staged+RC+Validation
Dev RC VOTE RESULT
To: dev@edgent.apache.org Subject: [RESULT][VOTE] Apache Edgent 1.2.0-incubating-RC1 PASSED The vote to accept RC1 passed with 8 +1 PMC/PPMC votes and no dissenting votes +1 Justin Mclean +1 Dale LaBossiere +1 Queenie Ma +1 Victor Dogaru +1 Susan Cline +1 Cazen Lee +1 Will Marshall +1 Dan Debrunner Thanks to all who voted! On to the next step - IPMC Release Approval VOTE
IPMC Release approval VOTE Email
To: general@incubator.apache.org
Cc: dev@edgent.apache.org
Subject: [VOTE] Publish Apache Edgent 1.2.0-incubating (RC1)
The Apache Edgent community approved a vote to release
Apache Edgent 1.2.0-incubating from RC1.
Per [1] we are requesting IPMC approval to publish the
source release bundles on the distribution site [2]
and binaries on Maven central.
This vote will be open for 72 hours.
- 1.2.0-incubating-RC1 vote results / thread [3]
- Git hash and tag for the release
commit: bbe71fa
tag: edgent-1.2.0
- link to RC1 source in the git repository [4]
- link to RC1 source bundle artifacts [5]
- link to RC1 Maven artifacts [6]
[ ] +1 accept
[ ] -1 reject (explanation required)
Thanks for your assistance in achieving this milestone!
[1] policy http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
[2] distribution https://dist.apache.org/repos/dist/release/incubator/edgent/
[3] rc1 vote https://www.mail-archive.com/dev@edgent.apache.org/msg00839.html
[4] rc1 src repo https://github.com/apache/incubator-edgent/tree/edgent-1.2.0
[5] rc1 artifacts https://dist.apache.org/repos/dist/dev/incubator/edgent/1.2.0-incubating/rc1/
[6] rc1 maven artifacts https://repository.apache.org/#stagingRepositories (log in with your Apache userId/pw)
or https://repository.apache.org/content/repositories/orgapacheedgent-XXXX
IPMC RESULT VOTE Email
To: general@incubator.apache.org Cc: dev@edgent.apache.org Subject: [RESULT][VOTE] Publish Apache Edgent 1.2.0-incubating (RC1) PASSED The IPMC vote to approve Apache Edgent 1.2.0-incubating (RC1) for release is now closed. [2] The vote PASSED: <n> accept (<m> binding), <n> reject (<m> binding) +1 ... (binding) +1 ... +1 ... (binding) +1 ... (binding) -1 ... Thank you to all who voted! [1] policy http://incubator.apache.org/incubation/Incubation_Policy.html#Releases [2] vote thread https://www.mail-archive.com/general@incubator.apache.org/msg57739.html
Announce
From: YOU@apache.org !!! To: announce@apache.org Cc: dev@edgent.apache.org Subject: [ANNOUNCE] Apache Edgent 1.2.0-incubating release The Apache Edgent project is pleased to announce release 1.2.0-incubating! Apache Edgent is a stream processing programming model and lightweight micro-kernel style runtime to execute analytics at devices on the edge or at the gateway. The release includes source code bundles. Convenience binaries are in Maven Central. Visit the Apache Edgent website [1] for general information or the downloads page [2] for release notes and download information. Regards, The Apache Edgent team [1] https://edgent.apache.org/ [2] https://edgent.apache.org/docs/downloads.html ===== *Disclaimer* Apache Edgent is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.