...
Run ./script vote_1\[git\]create_rc_tag.sh Example of script output:
...
? Probably this should be done using https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
For build number requested in this build step configuration, you should take build number (Teamcity identification of builds) from release candidate preparation Run Configuration from step 4.2.1.
...
All community members are encouraged to verify release. PMC members have a binding vote, but each vote matters.
...
Following list are steps, which can be done by each member, see also https://www.apache.org/info/verification.html
It is not complete list, community members can test any module or feature of the product.
Check that all JIRA issues for the specific version are Closed (example JQL: `project = IGNITE AND fixVersion <= 1.7 AND status != closed`).
Code Block | ||
---|---|---|
| ||
curl "https://issues.apache.org/jira/rest/api/2/search?jql=project=ignite%20AND%20status%20!=%20closed%20AND%20fixVersion<=1.7&fields=summary" | grep '"total":0,"issues":\[\]' |
Check that sha1 & md5 checksum is correct.
Code Block | ||
---|---|---|
| ||
sha1sum -c *.sha1 md5sum -c *.md5 |
Check that signature is correct.
Code Block | ||
---|---|---|
| ||
gpg --verify-files *.asc |
Check licenses from the source code.
Code Block | ||
---|---|---|
| ||
mvn clean validate -DskipTests=true -P check-licenses |
Build the binary releases from the source code.
Code Block | ||
---|---|---|
| ||
mvn clean package -DskipTests -Dignite.edition=hadoop mvn clean package -DskipTests |
Build Ignite.NET binaries and NuGet packages
Code Block | ||
---|---|---|
| ||
cd modules\platforms\dotnet build -skipJava |
...
After vote passes someone from PMC should do the following:
...
Send an email with subject "[RESULT] <vote subject>" ("[RESULT] [VOTE] Release Apache Ignite <version> (<rc>)") and provide vote results: if it passes or not, provide voting details.
For example, "[RESULT] [VOTE] Release Apache Ignite 2.7.5 (RC1)" and body similar to 2.7.5 vote result, 2.7.0 vote result . See also other example:
Expand | ||||
---|---|---|---|---|
|
...
svn import apache-ignite-fabric-<version>-bin/docs https://svn.apache.org/repos/asf/ignite/site/trunk/releases/<version> -m "new Release (<version>)"
...
Move release to https://dist.apache.org/repos/dist/release/ignite/<version>
Code Block | ||
---|---|---|
| ||
svn mv https://dist.apache.org/repos/dist/dev/ignite/<version><rc> https://dist.apache.org/repos/dist/release/ignite/<version> -m "Release <version>" |
Create Release tag from RC tag
Code Block | ||
---|---|---|
| ||
git tag -a <version> -m "<version>"
git push origin <version> |
|
In case vote is unsuccessful or closed by release manager, prepare new release candidate with fixes starting from step 4.2
In case vote was sucessfull, run release* scripts from RC home
Run release_1[svn]move_binaries.sh Example of output
Expand | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Manual alternative of this script is move release to https://dist.apache.org/repos/dist/release/ignite/<version>
|
Please check results at:
* binaries: https://apache.org/dist/ignite/{version} ← sync issue or delay here ?
Result should be available at https://dist.apache.org/repos/dist/release/ignite/
Upload documentation to https://svn.apache.org/repos/asf/ignite/site/trunk/releases/<version>
Code Block | ||
---|---|---|
| ||
svn import apache-ignite-fabric-<version>-bin/docs https://svn.apache.org/repos/asf/ignite/site/trunk/releases/<version> -m "new Release (<version>)" |
Create Release tag from RC tag
Code Block | ||
---|---|---|
| ||
git tag -a <version> -m "<version>"
git push origin <version> |
...
Send an email with subject "[RESULT] [VOTE] Apache Ignite <version> Release (<rc>)", for example "[RESULT] [VOTE] Apache Ignite 1.4.0 Release (RC1)" and body similar to:
Code Block | ||
---|---|---|
| ||
Hello!
Apache Ignite 1.4.0 release (RC1) has been accepted.
9 "+1" votes received.
Here are the votes received:
- Denis Magda (binding)
- Anton Vinogradov (binding)
- Alexey Kuznetsov (binding)
- Sergi Vladykin (binding)
- Gianfranco Murador (binding)
- Vladimir Ozerov (binding)
- Raul Kripalani (binding)
- Konstantin Boudnik (binding)
- Chandresh Pancholi
Here is the link to vote thread -
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-4-0-Release-RC1-tp3474.html
Ignite 1.4.0 successfuly released to https://dist.apache.org/repos/dist/release/ignite/1.4.0/
Thanks! |
After successful vote following actions should be done:
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Warning |
---|
1. Can committer be release manager and upload artifacts provided that PMC will upload committer's key 2. Steps to be done for prepare Nuget packages 3. Steps to be done for prepare RPM/DEB packages - step 4.3.3.1 4. https://apache.org/dist/ignite/{version} ← sync issue or delay here ? |