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

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

Royale_Release_Step_010 - Build # 29 - Failure!

[apacheroyaleci]

Royale_Release_Step_010 - Build # 29 - Failure:

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

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.

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

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

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

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.

RE: [DISCUSS] Discuss Release Apache Royale 0.9.8 RC4

[Yishay Weiss]

I will start a new RC tomorrow. Someone please cancel the vote on RC4 as I 
don’t have the original thread. Other than Josh, has anyone else got comments 
before I start this?

Thanks

From: Yishay Weiss
Sent: Saturday, July 24, 2021 7:00 PM
To: dev@royale.apache.org
Cc: Piotr Zarzycki
Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.8 RC4

I’ll have a look.

FYI, it looks like I’m not getting dev mails again (Piotr forwarded me this 
one). Maybe best to include my private email in these discussions for now.

It looks like RC5 is on the way, which will give us a chance to fix the NOTICE 
issues as well.

Thanks for the acknowledgement, Josh, and for the help you’ve provided so far. 
It’s not over yet…

From: Piotr Zarzycki
Sent: Saturday, July 24, 2021 6:41 PM
To: Yishay Weiss
Subject: Fwd: [DISCUSS] Discuss Release Apache Royale 0.9.8 RC4



-- Forwarded message -
From: Josh Tynjala mailto:joshtynj...@bowlerhat.dev>>
Date: Fri, 23 Jul 2021 at 19:14
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.8 RC4
To: Apache Royale Development 
mailto:dev@royale.apache.org>>


To clarify, the Ant targets that I mention in this post are stage-source
and stage-compiler in royale-compiler/build.xml. There's also a
stage-source in royale-asjs/build.xml, but that's different.

--
Josh Tynjala
Bowler Hat LLC 


On Fri, Jul 23, 2021 at 9:51 AM Josh Tynjala 
mailto:joshtynj...@bowlerhat.dev>>
wrote:

> It looks like the compiler-playerglobalc directory is missing from the
> source bundle. This causes the build to fail when running the approval
> script.
>
> In build.xml, I think that stage-source (or one of the other targets that
> it calls) needs to be updated to include compiler-playerglobalc. In
> stage-compiler, you can see how it copies the files for the other compiler
> modules. It's probably as easy as copy-pasting the section for
> compiler-externc and changing the compiler-externc paths to
> compiler-playerglobalc.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Fri, Jul 23, 2021 at 8:14 AM 
> mailto:apacheroyal...@gmail.com>> wrote:
>
>> This is the discussion thread.
>>
>> Thanks,
>> Yishay Weiss
>
>
--

Piotr Zarzycki

RE: [DISCUSS] Discuss Release Apache Royale 0.9.8 RC4

[Yishay Weiss]

I’ll have a look.

FYI, it looks like I’m not getting dev mails again (Piotr forwarded me this 
one). Maybe best to include my private email in these discussions for now.

It looks like RC5 is on the way, which will give us a chance to fix the NOTICE 
issues as well.

Thanks for the acknowledgement, Josh, and for the help you’ve provided so far. 
It’s not over yet…

From: Piotr Zarzycki
Sent: Saturday, July 24, 2021 6:41 PM
To: Yishay Weiss
Subject: Fwd: [DISCUSS] Discuss Release Apache Royale 0.9.8 RC4



-- Forwarded message -
From: Josh Tynjala mailto:joshtynj...@bowlerhat.dev>>
Date: Fri, 23 Jul 2021 at 19:14
Subject: Re: [DISCUSS] Discuss Release Apache Royale 0.9.8 RC4
To: Apache Royale Development 
mailto:dev@royale.apache.org>>


To clarify, the Ant targets that I mention in this post are stage-source
and stage-compiler in royale-compiler/build.xml. There's also a
stage-source in royale-asjs/build.xml, but that's different.

--
Josh Tynjala
Bowler Hat LLC 


On Fri, Jul 23, 2021 at 9:51 AM Josh Tynjala 
mailto:joshtynj...@bowlerhat.dev>>
wrote:

> It looks like the compiler-playerglobalc directory is missing from the
> source bundle. This causes the build to fail when running the approval
> script.
>
> In build.xml, I think that stage-source (or one of the other targets that
> it calls) needs to be updated to include compiler-playerglobalc. In
> stage-compiler, you can see how it copies the files for the other compiler
> modules. It's probably as easy as copy-pasting the section for
> compiler-externc and changing the compiler-externc paths to
> compiler-playerglobalc.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Fri, Jul 23, 2021 at 8:14 AM 
> mailto:apacheroyal...@gmail.com>> wrote:
>
>> This is the discussion thread.
>>
>> Thanks,
>> Yishay Weiss
>
>
--

Piotr Zarzycki

Re: [DISCUSS] Discuss Release Apache Royale 0.9.8 RC4

[Piotr Zarzycki]

Hi,

Yishay for some reason do not get any dev emails. I will forward to him
that.

On Fri, 23 Jul 2021 at 19:14, Josh Tynjala 
wrote:

> To clarify, the Ant targets that I mention in this post are stage-source
> and stage-compiler in royale-compiler/build.xml. There's also a
> stage-source in royale-asjs/build.xml, but that's different.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Fri, Jul 23, 2021 at 9:51 AM Josh Tynjala 
> wrote:
>
> > It looks like the compiler-playerglobalc directory is missing from the
> > source bundle. This causes the build to fail when running the approval
> > script.
> >
> > In build.xml, I think that stage-source (or one of the other targets that
> > it calls) needs to be updated to include compiler-playerglobalc. In
> > stage-compiler, you can see how it copies the files for the other
> compiler
> > modules. It's probably as easy as copy-pasting the section for
> > compiler-externc and changing the compiler-externc paths to
> > compiler-playerglobalc.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Fri, Jul 23, 2021 at 8:14 AM  wrote:
> >
> >> This is the discussion thread.
> >>
> >> Thanks,
> >> Yishay Weiss
> >
> >
>
-- 

Piotr Zarzycki