This is the discussion thread.
Thanks,
Yishay Weiss
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:
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"
Folder 0.9.9 already exists.
Continue to next step.
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
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.
This is the discussion thread.
Thanks,
Yishay Weiss
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:
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"
Folder 0.9.9 already exists.
Continue to next step.
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
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.
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.
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.
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.
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_010/35/
to view the results.
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.
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.
>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
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_007/27/
to view the results.
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.
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/25/
to view the results.
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/39/
to view the results.
>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
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:
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:
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/68/
to view the results.
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.
>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
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/66/
to view the results.
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.
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:
This is the discussion thread.
Thanks,
Yishay Weiss
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."
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.
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.
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
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.
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.
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_011/24/
to view the results.
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.
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.
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.
>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
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.
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.
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:
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:
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:
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:
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/32/
to view the results.
>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
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.
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:
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:
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:
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/50/
to view the results.
>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
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.
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.
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.
>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
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.
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.
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.
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:
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/29/
to view the results.
>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
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.
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.
This is the discussion thread.
Thanks,
Yishay Weiss
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:
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. "
Folder 0.9.8 already exists.
Continue to next step.
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
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.
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.
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.
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.
>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
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.
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:
Check console output at
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/21/
to view the results.
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.
>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
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.
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.
This is the discussion thread.
Thanks,
Yishay Weiss
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:
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."
1 - 100 of 3498 matches
Mail list logo