[DISCUSS] Discuss Release Apache Royale 0.9.9 RC4
This is the discussion thread. Thanks, Yishay Weiss
[VOTE] Release Apache Royale 0.9.9 RC4
Hi, This is the vote for the 0.9.9 release of Apache Royale. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/ Before voting please review the section,'What are the ASF requirements on approving a release?', at: http://www.apache.org/dev/release.html#approving-a-release At a minimum you would be expected to check that: - SHA and signed packages are correct - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine - That the build script completes successfully - That you can compile and crosscompile a simple example using the SDK. The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS The source package is a combination of the 3 main Royale repos. To use the binary package, unzip it into a folder. The -js package is ready-to-use in an IDE or command-line. If you need SWF output, use the -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via: ant -f InstallAdobeSDKs.xml You may also get the binarypackages via NPM. The -js package can be installed via: npm install https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/binaries/apache-royale-0.9.9-bin-js.tar.gz The full package with SWF support can be installed via: npm install https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/binaries/apache-royale-0.9.9-bin-js-swf.tar.gz Maven artifacts are staged here: https://repository.apache.org/content/repositories/orgapacheroyale-1091 Please vote to approve this release: +1 Approve the release -1 Disapprove the release (please provide specific comments to why) This vote will be open for 72 hours or until a result can be called. The vote passes if there is: - At least 3 +1 votes from the PMC - More positive votes than negative votes Remember that this is a 'beta-quality' release so expect there will be many bugs found. IMO the goal is not to try to find and fix bugs in the RC, but to make sure we have the packaging right, and enough functionality that folks will have some success trying to use it. People who are not in PMC are also encouraged to test out the release and vote, although their votes will not be binding, they can influence how the PMC votes. When voting please indicate what OS, IDE, Flash Player version and AIR version you tested with. For your convenience, there is an ant script that automates the common steps to validate a release. Instead of individually downloading the package and signature files, unzipping, etc, you can instead: 1) create an empty folder, 2) download into that folder this file: https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc4/ApproveRoyale.xml 3) run the script: ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=4 If you want to test SWF support during the approval, use: ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=4 -Duse-flash=true You are not required to use this script, and more testing of the packages and build results are always encouraged. Please put all discussion about this release in the DISCUSSION thread not this VOTE thread. Thanks, Yishay Weiss
Release Step 013 Succeeded
Note: before running these steps make sure that PLAYERGLOBAL_HOME is set and that you have PlayerGlobal installed under /11.7/playerglobal.swc >From the royale-asjs repo 1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.9 -Droyale.swc-date="2/10/22 9:06 -0800" -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=4 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_013_Sign -Drelease.version=0.9.9 This will PGP sign the source and convenience binary packages 4. Then run ant -f releasesteps.xml Release_Step_013_Upload -Drelease.version=0.9.9 -Drc=4 This will upload the signed artifacts to dist.apache.org.
Release Step 012 Succeeded
Folder 0.9.9 already exists. Continue to next step.
Release Step 011 Succeeded
Warning: this step requires a secret key, so it should not be performed on the CI server. It's probably best to perform it on your PC. >From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.9 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_011_Sign -Drelease.version=0.9.9 This will PGP sign the source ZIP and compiled JARs 4. Then run ant -f releasesteps.xml Release_Step_011_Upload -Drelease.version=0.9.9 This will upload the signed artifacts to Maven Release Staging. Verify that the compiler and typedefs artifacts are there along with the asjs artifacts, then hit the close to close the staging repo. (https://repository.apache.org/)
Release Step 010 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.9-rc4 You will need your Apache/Github username and 2FA token.
[DISCUSS] Discuss Release Apache Royale 0.9.9 RC3
This is the discussion thread. Thanks, Yishay Weiss
[VOTE] Release Apache Royale 0.9.9 RC3
Hi, This is the vote for the 0.9.9 release of Apache Royale. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc3/ Before voting please review the section,'What are the ASF requirements on approving a release?', at: http://www.apache.org/dev/release.html#approving-a-release At a minimum you would be expected to check that: - SHA and signed packages are correct - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine - That the build script completes successfully - That you can compile and crosscompile a simple example using the SDK. The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS The source package is a combination of the 3 main Royale repos. To use the binary package, unzip it into a folder. The -js package is ready-to-use in an IDE or command-line. If you need SWF output, use the -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via: ant -f InstallAdobeSDKs.xml You may also get the binarypackages via NPM. The -js package can be installed via: npm install https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc3/binaries/apache-royale-0.9.9-bin-js.tar.gz The full package with SWF support can be installed via: npm install https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc3/binaries/apache-royale-0.9.9-bin-js-swf.tar.gz Maven artifacts are staged here: https://repository.apache.org/content/repositories/orgapacheroyale-1090 Please vote to approve this release: +1 Approve the release -1 Disapprove the release (please provide specific comments to why) This vote will be open for 72 hours or until a result can be called. The vote passes if there is: - At least 3 +1 votes from the PMC - More positive votes than negative votes Remember that this is a 'beta-quality' release so expect there will be many bugs found. IMO the goal is not to try to find and fix bugs in the RC, but to make sure we have the packaging right, and enough functionality that folks will have some success trying to use it. People who are not in PMC are also encouraged to test out the release and vote, although their votes will not be binding, they can influence how the PMC votes. When voting please indicate what OS, IDE, Flash Player version and AIR version you tested with. For your convenience, there is an ant script that automates the common steps to validate a release. Instead of individually downloading the package and signature files, unzipping, etc, you can instead: 1) create an empty folder, 2) download into that folder this file: https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc3/ApproveRoyale.xml 3) run the script: ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=3 If you want to test SWF support during the approval, use: ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=3 -Duse-flash=true You are not required to use this script, and more testing of the packages and build results are always encouraged. Please put all discussion about this release in the DISCUSSION thread not this VOTE thread. Thanks, Yishay Weiss
Release Step 013 Succeeded
Note: before running these steps make sure that PLAYERGLOBAL_HOME is set and that you have PlayerGlobal installed under /11.7/playerglobal.swc >From the royale-asjs repo 1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.9 -Droyale.swc-date="2/10/22 9:06 -0800" -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=3 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_013_Sign -Drelease.version=0.9.9 This will PGP sign the source and convenience binary packages 4. Then run ant -f releasesteps.xml Release_Step_013_Upload -Drelease.version=0.9.9 -Drc=3 This will upload the signed artifacts to dist.apache.org.
Release Step 012 Succeeded
Folder 0.9.9 already exists. Continue to next step.
Release Step 011 Succeeded
Warning: this step requires a secret key, so it should not be performed on the CI server. It's probably best to perform it on your PC. >From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.9 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_011_Sign -Drelease.version=0.9.9 This will PGP sign the source ZIP and compiled JARs 4. Then run ant -f releasesteps.xml Release_Step_011_Upload -Drelease.version=0.9.9 This will upload the signed artifacts to Maven Release Staging. Verify that the compiler and typedefs artifacts are there along with the asjs artifacts, then hit the close to close the staging repo. (https://repository.apache.org/)
Release Step 010 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.9-rc3 You will need your Apache/Github username and 2FA token.
Release Step 009 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Release Step 008 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands: git push git checkout release/0.9.9 git push -u origin refs/heads/release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 009 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Release Step 008 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands: git push git checkout release/0.9.9 git push -u origin refs/heads/release/0.9.9 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_010 - Build # 35 - Failure!
Royale_Release_Step_010 - Build # 35 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_010/35/ to view the results.
Release Step 009 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Release Step 008 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands: git push git checkout release/0.9.9 git push -u origin refs/heads/release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 007 Succeeded
>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.9 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign -Drelease.version=0.9.9 This will PGP sign the source ZIP and compiled JARs 4. Then run ant -f releasesteps.xml Release_Step_007_Upload -Drelease.version=0.9.9 This will upload the signed artifacts to Maven Release Staging. Do not "Close" the staging repository until the other repos have been added.
Royale_Release_Step_007 - Build # 28 - Still Failing!
Royale_Release_Step_007 - Build # 28 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_007/28/ to view the results.
Royale_Release_Step_007 - Build # 27 - Failure!
Royale_Release_Step_007 - Build # 27 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_007/27/ to view the results.
Release Step 006 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands: git push git push origin org.apache.royale.typedefs-0.9.9-rc3 You will need your Apache/Github username and 2FA token.
Release Step 005 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Royale_Release_Step_005 - Build # 25 - Failure!
Royale_Release_Step_005 - Build # 25 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/25/ to view the results.
Release Step 004 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_004 - Build # 39 - Failure!
Royale_Release_Step_004 - Build # 39 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/39/ to view the results.
Release Step 003 Succeeded
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign
-Drelease.version=0.9.9
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload
-Drelease.version=0.9.9
This will upload the signed artifacts to Maven Release Staging. If you are
getting 401 responses from Nexus (permission denied) please be sure to have
your apache creedentials configured in your .m2/settings.xml file.
Feel free to use this template if you haven't got a settings.xml yet:
http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
apache.releases.https
{your apache user id}
{your apache user password}
(Be sure to replace the placeholders with your actual apache committer id and
your Apache password)
If you already have a settings.xml, just be sure the "server" block containing
your credentials is added to a servers block in that file.
Do not "Close" the staging repository until the other repos have been added.
Release Step 002 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.9-rc3 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_002 - Build # 70 - Still Failing!
Royale_Release_Step_002 - Build # 70 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/70/ to view the results.
Royale_Release_Step_002 - Build # 69 - Still Failing!
Royale_Release_Step_002 - Build # 69 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/69/ to view the results.
Royale_Release_Step_002 - Build # 68 - Failure!
Royale_Release_Step_002 - Build # 68 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/68/ to view the results.
Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 003 Succeeded
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign
-Drelease.version=0.9.9
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload
-Drelease.version=0.9.9
This will upload the signed artifacts to Maven Release Staging. If you are
getting 401 responses from Nexus (permission denied) please be sure to have
your apache creedentials configured in your .m2/settings.xml file.
Feel free to use this template if you haven't got a settings.xml yet:
http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
apache.releases.https
{your apache user id}
{your apache user password}
(Be sure to replace the placeholders with your actual apache committer id and
your Apache password)
If you already have a settings.xml, just be sure the "server" block containing
your credentials is added to a servers block in that file.
Do not "Close" the staging repository until the other repos have been added.
Release Step 002 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.9-rc3 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_002 - Build # 66 - Failure!
Royale_Release_Step_002 - Build # 66 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/66/ to view the results.
Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
[VOTE] Release Apache Royale 0.9.9 RC2
Hi, This is the vote for the 0.9.9 release of Apache Royale. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc2/ Before voting please review the section,'What are the ASF requirements on approving a release?', at: http://www.apache.org/dev/release.html#approving-a-release At a minimum you would be expected to check that: - SHA and signed packages are correct - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine - That the build script completes successfully - That you can compile and crosscompile a simple example using the SDK. The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS The source package is a combination of the 3 main Royale repos. To use the binary package, unzip it into a folder. The -js package is ready-to-use in an IDE or command-line. If you need SWF output, use the -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via: ant -f InstallAdobeSDKs.xml You may also get the binarypackages via NPM. The -js package can be installed via: npm install https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc2/binaries/apache-royale-0.9.9-bin-js.tar.gz The full package with SWF support can be installed via: npm install https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc2/binaries/apache-royale-0.9.9-bin-js-swf.tar.gz Maven artifacts are staged here: https://repository.apache.org/content/repositories/orgapacheroyale-1089 Please vote to approve this release: +1 Approve the release -1 Disapprove the release (please provide specific comments to why) This vote will be open for 72 hours or until a result can be called. The vote passes if there is: - At least 3 +1 votes from the PMC - More positive votes than negative votes Remember that this is a 'beta-quality' release so expect there will be many bugs found. IMO the goal is not to try to find and fix bugs in the RC, but to make sure we have the packaging right, and enough functionality that folks will have some success trying to use it. People who are not in PMC are also encouraged to test out the release and vote, although their votes will not be binding, they can influence how the PMC votes. When voting please indicate what OS, IDE, Flash Player version and AIR version you tested with. For your convenience, there is an ant script that automates the common steps to validate a release. Instead of individually downloading the package and signature files, unzipping, etc, you can instead: 1) create an empty folder, 2) download into that folder this file: https://dist.apache.org/repos/dist/dev/royale/0.9.9/rc2/ApproveRoyale.xml 3) run the script: ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=2 If you want to test SWF support during the approval, use: ant -e -f ApproveRoyale.xml -Drelease.version=0.9.9 -Drc=2 -Duse-flash=true You are not required to use this script, and more testing of the packages and build results are always encouraged. Please put all discussion about this release in the DISCUSSION thread not this VOTE thread. Thanks, Yishay Weiss
[DISCUSS] Discuss Release Apache Royale 0.9.9 RC2
This is the discussion thread. Thanks, Yishay Weiss
Release Step 013 Succeeded
Note: before running these steps make sure that PLAYERGLOBAL_HOME is set and that you have PlayerGlobal installed under /11.7/playerglobal.swc >From the royale-asjs repo 1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.9 -Droyale.swc-date="2/10/22 9:06 -0800." -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=2 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_013_Sign -Drelease.version=0.9.9 This will PGP sign the source and convenience binary packages 4. Then run ant -f releasesteps.xml Release_Step_013_Upload -Drelease.version=0.9.9 -Drc=2 This will upload the signed artifacts to dist.apache.org.
Release Step 012 Succeeded
Folder 0.9.9 created. Login to CI server. Change directory to C:\jenkins\workspace\Royale_Release_Step_012\dist\dev\royale. Run 'svn commit -m "add version folder"' You will need your svn username and password.
Release Step 012 Succeeded
Folder 0.9.9 created. Login to CI server. Change directory to C:\jenkins\workspace\Royale_Release_Step_012\dist\dev\royale. Run 'svn commit -m "add version folder"' You will need your svn username and password.
Release Step 011 Succeeded
Warning: this step requires a secret key, so it should not be performed on the CI server. It's probably best to perform it on your PC. >From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.9 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_011_Sign -Drelease.version=0.9.9 This will PGP sign the source ZIP and compiled JARs 4. Then run ant -f releasesteps.xml Release_Step_011_Upload -Drelease.version=0.9.9 This will upload the signed artifacts to Maven Release Staging. Verify that the compiler and typedefs artifacts are there along with the asjs artifacts, then hit the close to close the staging repo. (https://repository.apache.org/)
Release Step 010 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.9-rc2 You will need your Apache/Github username and 2FA token.
Release Step 009 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Release Step 008 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands: git push git checkout release/0.9.9 git push -u origin refs/heads/release/0.9.9 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_011 - Build # 24 - Failure!
Royale_Release_Step_011 - Build # 24 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/24/ to view the results.
Release Step 010 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.9-rc2 You will need your Apache/Github username and 2FA token.
Release Step 009 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Release Step 008 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands: git push git checkout release/0.9.9 git push -u origin refs/heads/release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 007 Succeeded
>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.9 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign -Drelease.version=0.9.9 This will PGP sign the source ZIP and compiled JARs 4. Then run ant -f releasesteps.xml Release_Step_007_Upload -Drelease.version=0.9.9 This will upload the signed artifacts to Maven Release Staging. Do not "Close" the staging repository until the other repos have been added.
Release Step 006 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands: git push git push origin org.apache.royale.typedefs-0.9.9-rc2 You will need your Apache/Github username and 2FA token.
Release Step 005 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Release Step 004 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_004 - Build # 36 - Still Failing!
Royale_Release_Step_004 - Build # 36 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/36/ to view the results.
Royale_Release_Step_004 - Build # 35 - Still Failing!
Royale_Release_Step_004 - Build # 35 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/35/ to view the results.
Royale_Release_Step_004 - Build # 34 - Still Failing!
Royale_Release_Step_004 - Build # 34 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/34/ to view the results.
Royale_Release_Step_004 - Build # 33 - Still Failing!
Royale_Release_Step_004 - Build # 33 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/33/ to view the results.
Royale_Release_Step_004 - Build # 32 - Failure!
Royale_Release_Step_004 - Build # 32 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/32/ to view the results.
Release Step 003 Succeeded
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign
-Drelease.version=0.9.9
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload
-Drelease.version=0.9.9
This will upload the signed artifacts to Maven Release Staging. If you are
getting 401 responses from Nexus (permission denied) please be sure to have
your apache creedentials configured in your .m2/settings.xml file.
Feel free to use this template if you haven't got a settings.xml yet:
http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
apache.releases.https
{your apache user id}
{your apache user password}
(Be sure to replace the placeholders with your actual apache committer id and
your Apache password)
If you already have a settings.xml, just be sure the "server" block containing
your credentials is added to a servers block in that file.
Do not "Close" the staging repository until the other repos have been added.
Release Step 002 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.9-rc2 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_001 - Build # 54 - Still Failing!
Royale_Release_Step_001 - Build # 54 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/54/ to view the results.
Royale_Release_Step_001 - Build # 53 - Still Failing!
Royale_Release_Step_001 - Build # 53 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/53/ to view the results.
Royale_Release_Step_001 - Build # 52 - Failure!
Royale_Release_Step_001 - Build # 52 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/52/ to view the results.
Royale_Release_Step_001 - Build # 50 - Failure!
Royale_Release_Step_001 - Build # 50 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/50/ to view the results.
Release Step 003 Succeeded
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign
-Drelease.version=0.9.9
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload
-Drelease.version=0.9.9
This will upload the signed artifacts to Maven Release Staging. If you are
getting 401 responses from Nexus (permission denied) please be sure to have
your apache creedentials configured in your .m2/settings.xml file.
Feel free to use this template if you haven't got a settings.xml yet:
http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
apache.releases.https
{your apache user id}
{your apache user password}
(Be sure to replace the placeholders with your actual apache committer id and
your Apache password)
If you already have a settings.xml, just be sure the "server" block containing
your credentials is added to a servers block in that file.
Do not "Close" the staging repository until the other repos have been added.
Release Step 002 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.9-rc2 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Release Step 007 Succeeded
>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.9 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign -Drelease.version=0.9.9 This will PGP sign the source ZIP and compiled JARs 4. Then run ant -f releasesteps.xml Release_Step_007_Upload -Drelease.version=0.9.9 This will upload the signed artifacts to Maven Release Staging. Do not "Close" the staging repository until the other repos have been added.
Royale_Release_Step_007 - Build # 24 - Failure!
Royale_Release_Step_007 - Build # 24 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_007/24/ to view the results.
Release Step 006 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands: git push git push origin org.apache.royale.typedefs-0.9.9-rc1 You will need your Apache/Github username and 2FA token.
Release Step 005 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Release Step 004 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
Royale_Release_Step_004 - Build # 30 - Still Failing!
Royale_Release_Step_004 - Build # 30 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/30/ to view the results.
Royale_Release_Step_004 - Build # 29 - Failure!
Royale_Release_Step_004 - Build # 29 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/29/ to view the results.
Release Step 003 Succeeded
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign
-Drelease.version=0.9.9
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload
-Drelease.version=0.9.9
This will upload the signed artifacts to Maven Release Staging. If you are
getting 401 responses from Nexus (permission denied) please be sure to have
your apache creedentials configured in your .m2/settings.xml file.
Feel free to use this template if you haven't got a settings.xml yet:
http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
apache.releases.https
{your apache user id}
{your apache user password}
(Be sure to replace the placeholders with your actual apache committer id and
your Apache password)
If you already have a settings.xml, just be sure the "server" block containing
your credentials is added to a servers block in that file.
Do not "Close" the staging repository until the other repos have been added.
Release Step 002 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.9-rc1 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.9 git push -u origin release/0.9.9 You will need your Apache/Github username and 2FA token.
[DISCUSS] Discuss Release Apache Royale 0.9.8 RC7
This is the discussion thread. Thanks, Yishay Weiss
[VOTE] Release Apache Royale 0.9.8 RC7
Hi, This is the vote for the 0.9.8 release of Apache Royale. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/0.9.8/rc7/ Before voting please review the section,'What are the ASF requirements on approving a release?', at: http://www.apache.org/dev/release.html#approving-a-release At a minimum you would be expected to check that: - SHA and signed packages are correct - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine - That the build script completes successfully - That you can compile and crosscompile a simple example using the SDK. The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS The source package is a combination of the 3 main Royale repos. To use the binary package, unzip it into a folder. The -js package is ready-to-use in an IDE or command-line. If you need SWF output, use the -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via: ant -f InstallAdobeSDKs.xml You may also get the binarypackages via NPM. The -js package can be installed via: npm install https://dist.apache.org/repos/dist/dev/royale/0.9.8/rc7/binaries/apache-royale-0.9.8-bin-js.tar.gz The full package with SWF support can be installed via: npm install https://dist.apache.org/repos/dist/dev/royale/0.9.8/rc7/binaries/apache-royale-0.9.8-bin-js-swf.tar.gz Maven artifacts are staged here: https://repository.apache.org/content/repositories/orgapacheroyale-1086 Please vote to approve this release: +1 Approve the release -1 Disapprove the release (please provide specific comments to why) This vote will be open for 72 hours or until a result can be called. The vote passes if there is: - At least 3 +1 votes from the PMC - More positive votes than negative votes Remember that this is a 'beta-quality' release so expect there will be many bugs found. IMO the goal is not to try to find and fix bugs in the RC, but to make sure we have the packaging right, and enough functionality that folks will have some success trying to use it. People who are not in PMC are also encouraged to test out the release and vote, although their votes will not be binding, they can influence how the PMC votes. When voting please indicate what OS, IDE, Flash Player version and AIR version you tested with. For your convenience, there is an ant script that automates the common steps to validate a release. Instead of individually downloading the package and signature files, unzipping, etc, you can instead: 1) create an empty folder, 2) download into that folder this file: https://dist.apache.org/repos/dist/dev/royale/0.9.8/rc7/ApproveRoyale.xml 3) run the script: ant -e -f ApproveRoyale.xml -Drelease.version=0.9.8 -Drc=7 If you want to test SWF support during the approval, use: ant -e -f ApproveRoyale.xml -Drelease.version=0.9.8 -Drc=7 -Duse-flash=true You are not required to use this script, and more testing of the packages and build results are always encouraged. Please put all discussion about this release in the DISCUSSION thread not this VOTE thread. Thanks, Yishay Weiss
Release Step 013 Succeeded
Note: before running these steps make sure that PLAYERGLOBAL_HOME is set and that you have PlayerGlobal installed under /11.7/playerglobal.swc >From the royale-asjs repo 1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.8 -Droyale.swc-date="08/27/21 9:06 -0800. " -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=7 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_013_Sign -Drelease.version=0.9.8 This will PGP sign the source and convenience binary packages 4. Then run ant -f releasesteps.xml Release_Step_013_Upload -Drelease.version=0.9.8 -Drc=7 This will upload the signed artifacts to dist.apache.org.
Release Step 012 Succeeded
Folder 0.9.8 already exists. Continue to next step.
Release Step 011 Succeeded
Warning: this step requires a secret key, so it should not be performed on the CI server. It's probably best to perform it on your PC. >From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.8 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_011_Sign -Drelease.version=0.9.8 This will PGP sign the source ZIP and compiled JARs 4. Then run ant -f releasesteps.xml Release_Step_011_Upload -Drelease.version=0.9.8 This will upload the signed artifacts to Maven Release Staging. Verify that the compiler and typedefs artifacts are there along with the asjs artifacts, then hit the close to close the staging repo. (https://repository.apache.org/)
Royale_Release_Step_011 - Build # 22 - Failure!
Royale_Release_Step_011 - Build # 22 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/22/ to view the results.
Release Step 010 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.8-rc7 You will need your Apache/Github username and 2FA token.
Release Step 009 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Release Step 008 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands: git push git checkout release/0.9.8 git push -u origin refs/heads/release/0.9.8 You will need your Apache/Github username and 2FA token.
Release Step 007 Succeeded
>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.8 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign -Drelease.version=0.9.8 This will PGP sign the source ZIP and compiled JARs 4. Then run ant -f releasesteps.xml Release_Step_007_Upload -Drelease.version=0.9.8 This will upload the signed artifacts to Maven Release Staging. Do not "Close" the staging repository until the other repos have been added.
Release Step 006 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands: git push git push origin org.apache.royale.typedefs-0.9.8-rc7 You will need your Apache/Github username and 2FA token.
Release Step 005 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands: git push You will need your Apache/Github username and 2FA token.
Royale_Release_Step_005 - Build # 21 - Failure!
Royale_Release_Step_005 - Build # 21 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/21/ to view the results.
Release Step 004 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands: git push git checkout release/0.9.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.
Release Step 003 Succeeded
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign
-Drelease.version=0.9.8
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload
-Drelease.version=0.9.8
This will upload the signed artifacts to Maven Release Staging. If you are
getting 401 responses from Nexus (permission denied) please be sure to have
your apache creedentials configured in your .m2/settings.xml file.
Feel free to use this template if you haven't got a settings.xml yet:
http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
apache.releases.https
{your apache user id}
{your apache user password}
(Be sure to replace the placeholders with your actual apache committer id and
your Apache password)
If you already have a settings.xml, just be sure the "server" block containing
your credentials is added to a servers block in that file.
Do not "Close" the staging repository until the other repos have been added.
Release Step 002 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.8-rc7 You will need your Apache/Github username and 2FA token.
Release Step 001 Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands: git push git checkout release/0.9.8 git push -u origin release/0.9.8 You will need your Apache/Github username and 2FA token.
[DISCUSS] Discuss Release Apache Royale 0.9.8 RC6
This is the discussion thread. Thanks, Yishay Weiss
[VOTE] Release Apache Royale 0.9.8 RC6
Hi, This is the vote for the 0.9.8 release of Apache Royale. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/0.9.8/rc6/ Before voting please review the section,'What are the ASF requirements on approving a release?', at: http://www.apache.org/dev/release.html#approving-a-release At a minimum you would be expected to check that: - SHA and signed packages are correct - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine - That the build script completes successfully - That you can compile and crosscompile a simple example using the SDK. The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS The source package is a combination of the 3 main Royale repos. To use the binary package, unzip it into a folder. The -js package is ready-to-use in an IDE or command-line. If you need SWF output, use the -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via: ant -f InstallAdobeSDKs.xml You may also get the binarypackages via NPM. The -js package can be installed via: npm install https://dist.apache.org/repos/dist/dev/royale/0.9.8/rc6/binaries/apache-royale-0.9.8-bin-js.tar.gz The full package with SWF support can be installed via: npm install https://dist.apache.org/repos/dist/dev/royale/0.9.8/rc6/binaries/apache-royale-0.9.8-bin-js-swf.tar.gz Maven artifacts are staged here: https://repository.apache.org/content/repositories/orgapacheroyale-1085 Please vote to approve this release: +1 Approve the release -1 Disapprove the release (please provide specific comments to why) This vote will be open for 72 hours or until a result can be called. The vote passes if there is: - At least 3 +1 votes from the PMC - More positive votes than negative votes Remember that this is a 'beta-quality' release so expect there will be many bugs found. IMO the goal is not to try to find and fix bugs in the RC, but to make sure we have the packaging right, and enough functionality that folks will have some success trying to use it. People who are not in PMC are also encouraged to test out the release and vote, although their votes will not be binding, they can influence how the PMC votes. When voting please indicate what OS, IDE, Flash Player version and AIR version you tested with. For your convenience, there is an ant script that automates the common steps to validate a release. Instead of individually downloading the package and signature files, unzipping, etc, you can instead: 1) create an empty folder, 2) download into that folder this file: https://dist.apache.org/repos/dist/dev/royale/0.9.8/rc6/ApproveRoyale.xml 3) run the script: ant -e -f ApproveRoyale.xml -Drelease.version=0.9.8 -Drc=6 If you want to test SWF support during the approval, use: ant -e -f ApproveRoyale.xml -Drelease.version=0.9.8 -Drc=6 -Duse-flash=true You are not required to use this script, and more testing of the packages and build results are always encouraged. Please put all discussion about this release in the DISCUSSION thread not this VOTE thread. Thanks, Yishay Weiss
Release Step 013 Succeeded
Note: before running these steps make sure that PLAYERGLOBAL_HOME is set and that you have PlayerGlobal installed under /11.7/playerglobal.swc >From the royale-asjs repo 1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.8 -Droyale.swc-date="08/15/21 9:06 -0800." -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=6 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f releasesteps.xml Release_Step_013_Sign -Drelease.version=0.9.8 This will PGP sign the source and convenience binary packages 4. Then run ant -f releasesteps.xml Release_Step_013_Upload -Drelease.version=0.9.8 -Drc=6 This will upload the signed artifacts to dist.apache.org.
