Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
titleDev 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.
 
At this point the 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 testing 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/
Code Block
titleDev DISCUSS email [update thread]
Reply to the [DISCUSS] thread...
 
Release branch master:release/1.2 has been created. 
Jenkins should be building and testing the branch [1].
The tag edgent-1.2.0 marks the release candidate's contents.




Future release development may now continue on theJenkins 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
Code Block
titledev@ 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

...