Release Step 012 Succeeded

[apacheroyaleci]

Folder 0.9.8 already exists.
Continue to next step.

Release Step 011 Succeeded

[apacheroyaleci]

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/)

Release Step 010 Succeeded

[apacheroyaleci]

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-rc6

You will need your Apache/Github username and 2FA token.

Release Step 009 Succeeded

[apacheroyaleci]

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.

Royale_Release_Step_009 - Build # 8 - Failure!

[apacheroyaleci]

Royale_Release_Step_009 - Build # 8 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_009/8/
 to view the results.

[CANCEL] [VOTE] Release Apache Royale 0.9.8 RC5

[Yishay Weiss]

Cancel vote in favor of RC6

On 2021/07/25 13:14:12, apacheroyal...@gmail.com wrote: 
> 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/rc5/
> 
> 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/rc5/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/rc5/binaries/apache-royale-0.9.8-bin-js-swf.tar.gz
> 
> Maven artifacts are staged here: 
> https://repository.apache.org/content/repositories/orgapacheroyale-1083
> 
> 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/rc5/ApproveRoyale.xml
> 3) run the script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.8 -Drc=5
>If you want to test SWF support during the approval, use:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.8 -Drc=5 -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 008 Succeeded

[apacheroyaleci]

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

[apacheroyaleci]

>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

[apacheroyaleci]

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-rc6

You will need your Apache/Github username and 2FA token.

Release Step 005 Succeeded

[apacheroyaleci]

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

[apacheroyaleci]

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

[apacheroyaleci]

>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

[apacheroyaleci]

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-rc6

You will need your Apache/Github username and 2FA token.

RE: Mustella Tests

[Yishay Weiss]

Thanks, looks good.

From: Edward Stangler
Sent: Saturday, August 14, 2021 3:54 AM
To: Yishay Weiss; 
dev@royale.apache.org
Subject: Re: Mustella Tests




PR #1146 fixes this.


On 8/13/2021 4:10 AM, Yishay Weiss wrote:
MX integration tests are still failing with a similar message. Note that his 
time it’s SetupListAndDataGridTest (not button test which passes).

Edward, do you think you can take a look?

I got the below message in my flash log

C:\Users\yisha\AppData\Roaming\Macromedia\Flash Player\Logs\flashlog.txt

After running

ant mxtests from royale-asjs

RESULT: 
scriptName=halo.scripts::ListAndDataGridTestScript=SetupListAndDataGridTest=fail=11=body=1628843604291==ArgumentError:
 Error #2024: An object cannot be added as a child of itself.^  at 
flash.display::DisplayObjectContainer/addChild()^at 
org.apache.royale.core::UIBase/$sprite_addChild()[/org/apache/royale/0.9.8/org/apache/royale/core/UIBase.as:1584]^
 at 
org.apache.royale.core::UIBase/addElement()[/org/apache/royale/0.9.8/org/apache/royale/core/UIBase.as:1175]^
  at 
mx.controls.listClasses::ListBase/addElement()[/org/apache/royale/0.9.8/mx/controls/listClasses/ListBase.as:1032]^
 at 
org.apache.royale.html.beads::ContainerView/addViewport()[/org/apache/royale/0.9.8/org/apache/royale/html/beads/ContainerView.as:169]^
  at org.apache.royale.html.beads::ContainerView/set 
strand()[/org/apache/royale/0.9.8/org/apache/royale/html/beads/ContainerView.as:155]^
  at org.apache.royale.html.beads::DataContainerView/set 
strand()[/org/apache/royale/0.9.8/org/apache/royale/html/beads/DataContainerView.as:75]^
   at 
org.apache.royale.core::HTMLElementWrapper/addBead()[/org/apache/royale/0.9.8/org/apache/royale/core/HTMLElementWrapper.as:66]^
   at 
org.apache.royale.core::UIBase/addBead()[/org/apache/royale/0.9.8/org/apache/royale/core/UIBase.as:1148]^
 at 
global/org.apache.royale.utils::loadBeadFromValuesManager()[/org/apache/royale/0.9.8/org/apache/royale/utils/loadBeadFromValuesManager.as:55]^
   at 
org.apache.royale.core::UIBase/loadBeads()[/org/apache/royale/0.9.8/org/apache/royale/core/UIBase.as:1419]^
 at 
org.apache.royale.core::UIBase/addedToParent()[/org/apache/royale/0.9.8/org/apache/royale/core/UIBase.as:1402]^
at 
mx.core::UIComponent/addedToParent()[/org/apache/royale/0.9.8/mx/core/UIComponent.as:2365]^
 at 
mx.controls.listClasses::ListBase/addedToParent()[/org/apache/royale/0.9.8/mx/controls/listClasses/ListBase.as:883]^
  at 
org.apache.royale.core::UIBase/addElement()[/org/apache/royale/0.9.8/org/apache/royale/core/UIBase.as:1178]^
  at 
mx.core::Container/addElement()[/org/apache/royale/0.9.8/mx/core/Container.as:1386]^
  at 
org.apache.royale.utils::MXMLDataInterpreter$/initializeStrandBasedObject()[/org/apache/royale/0.9.8/org/apache/royale/utils/MXMLDataInterpreter.as:307]^
   at 
org.apache.royale.utils::MXMLDataInterpreter$/generateMXMLArray()[/org/apache/royale/0.9.8/org/apache/royale/utils/MXMLDataInterpreter.as:157]^
   at 
org.apache.royale.utils::MXMLDataInterpreter$/generateMXMLInstances()[/org/apache/royale/0.9.8/org/apache/royale/utils/MXMLDataInterpreter.as:337]^
 at 
mx.core::UIComponent/createChildren()[/org/apache/royale/0.9.8/mx/core/UIComponent.as:4166]^
  at 
mx.core::Container/createChildren()[/org/apache/royale/0.9.8/mx/core/Container.as:1101]^
   at 
mx.core::UIComponent/initialize()[/org/apache/royale/0.9.8/mx/core/UIComponent.as:4112]^
   at 
mx.core::UIComponent/addedToParent()[/org/apache/royale/0.9.8/mx/core/UIComponent.as:2382]^
 at 
mx.core::Container/addedToParent()[/org/apache/royale/0.9.8/mx/core/Container.as:1089]^
 at 
mx.containers::Box/addedToParent()[/org/apache/royale/0.9.8/mx/containers/Box.as:229]^
at 
org.apache.royale.core::UIBase/addElementAt()[/org/apache/royale/0.9.8/org/apache/royale/core/UIBase.as:1209]^
  at 
mx.core::Container/addElementAt()[/org/apache/royale/0.9.8/mx/core/Container.as:1398]^
   at 
org.apache.royale.core::StatesWithTransitionsImpl/apply()[/org/apache/royale/0.9.8/org/apache/royale/core/StatesWithTransitionsImpl.as:361]^
at 
org.apache.royale.core::StatesWithTransitionsImpl/stateChangeHandler()[/org/apache/royale/0.9.8/org/apache/royale/core/StatesWithTransitionsImpl.as:162]^
   at flash.events::EventDispatcher/dispatchEventFunction()^   at 
flash.events::EventDispatcher/dispatchEvent()^  at 
org.apache.royale.core::UIBase/dispatchEvent()[/org/apache/royale/0.9.8/org/apache/royale/core/UIBase.as:1577]^
  at mx.core::UIComponent/set 
currentState()[/org/apache/royale/0.9.8/mx/core/UIComponent.as:3550]^   
at 
SetProperty/doStep()[C:/dev/full_royale_sdk/royale-asjs/mustella/src/main/royale/SetProperty.as:90]^
   at 
TestStep/execute()[C:/dev/full_royale_sdk/royale-asjs/mustella/src/main/royale/TestStep.as:75]^
  at 

Release Step 001 Succeeded

[apacheroyaleci]

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.