Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-11 Thread Carlos Rovira
Hi

website update is now complete

El mar., 11 dic. 2018 a las 23:06, Carlos Rovira ()
escribió:

> Hi
>
> just make a page on GitHub to document how to publish website changes, so
> others can do this.
> Since there's is some find and replacement operations needed, that I put
> in this mailing list, but are hard to find I think this was needed.
>
> Athough I think I'll continue updating the website, is good to show the
> process so others can do it if they want
>
> New page is as well added to the end of right menu in Release manager
> notes. This is the page
>
> https://github.com/apache/royale-asjs/wiki/Release-Manger-(Web-Site)
>
>
>
>
>
>
> El mar., 11 dic. 2018 a las 20:31, Carlos Rovira ()
> escribió:
>
>> Hi Andrew,
>>
>> the source code is JewelExample here:
>>
>>
>> https://github.com/apache/royale-asjs/tree/develop/examples/royale/JewelExample
>>
>> as well if you go to the Alert part, you'll see a tab navigator (still in
>> development so a bit ugly yet), with a tab with the example and other that
>> points to the source code for that part
>>
>> I must to do this for all examples, so if you like it, you could help
>> doing this for each example. I think I could make still more easy like a
>> component and just replicate in all examples inside the tour :)
>>
>> If you want to help me with this part, let me know and we can plan ;)
>>
>>
>>
>>
>> El mar., 11 dic. 2018 a las 19:46, Andrew Wetmore ()
>> escribió:
>>
>>> This is fun to play with! Where is the source code for each example?
>>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-11 Thread Carlos Rovira
Hi

just make a page on GitHub to document how to publish website changes, so
others can do this.
Since there's is some find and replacement operations needed, that I put in
this mailing list, but are hard to find I think this was needed.

Athough I think I'll continue updating the website, is good to show the
process so others can do it if they want

New page is as well added to the end of right menu in Release manager
notes. This is the page

https://github.com/apache/royale-asjs/wiki/Release-Manger-(Web-Site)






El mar., 11 dic. 2018 a las 20:31, Carlos Rovira ()
escribió:

> Hi Andrew,
>
> the source code is JewelExample here:
>
>
> https://github.com/apache/royale-asjs/tree/develop/examples/royale/JewelExample
>
> as well if you go to the Alert part, you'll see a tab navigator (still in
> development so a bit ugly yet), with a tab with the example and other that
> points to the source code for that part
>
> I must to do this for all examples, so if you like it, you could help
> doing this for each example. I think I could make still more easy like a
> component and just replicate in all examples inside the tour :)
>
> If you want to help me with this part, let me know and we can plan ;)
>
>
>
>
> El mar., 11 dic. 2018 a las 19:46, Andrew Wetmore ()
> escribió:
>
>> This is fun to play with! Where is the source code for each example?
>>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-11 Thread Carlos Rovira
Hi Andrew,

the source code is JewelExample here:

https://github.com/apache/royale-asjs/tree/develop/examples/royale/JewelExample

as well if you go to the Alert part, you'll see a tab navigator (still in
development so a bit ugly yet), with a tab with the example and other that
points to the source code for that part

I must to do this for all examples, so if you like it, you could help doing
this for each example. I think I could make still more easy like a
component and just replicate in all examples inside the tour :)

If you want to help me with this part, let me know and we can plan ;)




El mar., 11 dic. 2018 a las 19:46, Andrew Wetmore ()
escribió:

> This is fun to play with! Where is the source code for each example?
>
-- 
Carlos Rovira
http://about.me/carlosrovira


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-11 Thread Andrew Wetmore
This is fun to play with! Where is the source code for each example?

On Tue, Dec 11, 2018 at 2:16 PM Carlos Rovira 
wrote:

> Hi all
>
> updates to the website are live. Although I saw there's still some few
> little issues, that I'll solve more later since I must to left right now.
>
> I added Jewel Example as "Tour de Jewel" in "Home" and "Feature" pages, so
> this points to: http://royale.apache.org/tourdejewel/
>
> More to share in a few hours.
>
> :)
>
> Carlos
>
>
>
>
>
>
>
>
> El lun., 10 dic. 2018 a las 18:30, Carlos Rovira (<
> carlos.rov...@codeoscopic.com>) escribió:
>
> > Ok Alex,
> >
> > I'll change the 2 links to http for now. Maybe it should make a
> difference
> > with browsers and google. If we have some problems we can check later.
> >
> > I'll wait an hour or so if someone want to make some other change before
> > publish.
> >
> > thanks!
> >
> > Carlos
> >
> >
> >
> >
> >
> >
> > El lun., 10 dic. 2018 a las 18:15, Alex Harui ( >)
> > escribió:
> >
> >> Hopefully the links to the CI server are not for release artifacts, but
> >> just nightly builds.
> >>
> >> If someone wants to pay for an HTTPS cert for our CI server, please do
> so
> >> and set it up.
> >>
> >> Otherwise, those links will have to be HTTP.  I don't see from a quick
> >> internet search that having a link to HTTP on a page will mean that the
> >> page containing the link is marked insecure.  But yes, when you go to
> the
> >> CI server it will say it isn't secure because it isn't.  Folks are
> taking
> >> chances using our nightly builds anyway.  Anyone who is concerned about
> the
> >> risk can build from sources.
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 12/10/18, 8:27 AM, "Carlos Rovira"  wrote:
> >>
> >> thanks Josh for looking this issue
> >>
> >> I think we can't remove the https, since all the site is secure and
> >> we need
> >> to enforce this to avoid problems with google.
> >> You should we change to http?
> >>
> >> Any suggestions are welcome
> >>
> >> thanks
> >>
> >>
> >>
> >>
> >> El lun., 10 dic. 2018 a las 16:55, Josh Tynjala (<
> >> joshtynj...@apache.org>)
> >> escribió:
> >>
> >> > Yeah, it's been like that for a while. This is the error that I
> see
> >> in
> >> > Firefox:
> >> >
> >> > Secure Connection Failed
> >> >
> >> > An error occurred during a connection to
> >> > apacheroyaleci.westus2.cloudapp.azure.com:8080. SSL received a
> >> record
> >> > that exceeded the maximum permissible length. Error code:
> >> > SSL_ERROR_RX_RECORD_TOO_LONG
> >> >
> >> > I guess that means that something is wrong with how the
> certificate
> >> is set
> >> > up.
> >> >
> >> > I've found that the links work if you change them from https to
> >> http.
> >> >
> >> > - Josh
> >> >
> >> > On 2018/12/10 14:44:06, Carlos Rovira 
> >> wrote:
> >> > > Hi,
> >> > >
> >> > > I'm updating the site, and I'm finding this tow links are not
> >> working:
> >> > >
> >> > > royale-asjs artifacts
> >> > > <
> >> >
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuild%2Fartifact%2Fout%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=5r4MtCUBRO1yb%2FxhlW2nTM4a%2F4PxQd1b9KftLLQCPqA%3D&reserved=0
> >> > >
> >> > > royale-asjs-jsonly artifacts
> >> > > <
> >> >
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=yPc%2B6Rv7h7xO00RB0nvQTzuMdKJbeigK5MmU4brffy0%3D&reserved=0
> >> > >
> >> > >
> >> > > (those are located at the end of download page, in pre-site the
> >> link is:
> >> > >
> >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fdownload%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=CYN40RLz2nXpS7gTBHfuZCSSq6M1rMFLJWksiSGll1U%3D&reserved=0
> >> )
> >> > >
> >> > > I'll continue updating things, if someone can let me know about
> >> this
> >> > before
> >> > > publish that will be great
> >> > >
> >> > > thanks!
> >> > >
> >> > >
> >> > >
> >> > > El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira (<
> >> > carlosrov...@apache.org>)
> >> > > escribió:
> >> > >
> >> > > > Thanks Piotr,
> >> > > >
> >> > > > I'll do this on Monday evening
> >> > > >
> >> > > > thanks
> >> > > >
> >> > > > Carlos
> >> > > >
> >> > > >
> >> > > > El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzyc

Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-11 Thread Carlos Rovira
Just one more thing :)

if you see something in r.a.o let me know so I can fix all that in the
fixes I'll do in few hours

thanks!

Carlos


El mar., 11 dic. 2018 a las 19:16, Carlos Rovira ()
escribió:

> Hi all
>
> updates to the website are live. Although I saw there's still some few
> little issues, that I'll solve more later since I must to left right now.
>
> I added Jewel Example as "Tour de Jewel" in "Home" and "Feature" pages, so
> this points to: http://royale.apache.org/tourdejewel/
>
> More to share in a few hours.
>
> :)
>
> Carlos
>
>
>
>
>
>
>
>
> El lun., 10 dic. 2018 a las 18:30, Carlos Rovira (<
> carlos.rov...@codeoscopic.com>) escribió:
>
>> Ok Alex,
>>
>> I'll change the 2 links to http for now. Maybe it should make a
>> difference with browsers and google. If we have some problems we can check
>> later.
>>
>> I'll wait an hour or so if someone want to make some other change before
>> publish.
>>
>> thanks!
>>
>> Carlos
>>
>>
>>
>>
>>
>>
>> El lun., 10 dic. 2018 a las 18:15, Alex Harui ()
>> escribió:
>>
>>> Hopefully the links to the CI server are not for release artifacts, but
>>> just nightly builds.
>>>
>>> If someone wants to pay for an HTTPS cert for our CI server, please do
>>> so and set it up.
>>>
>>> Otherwise, those links will have to be HTTP.  I don't see from a quick
>>> internet search that having a link to HTTP on a page will mean that the
>>> page containing the link is marked insecure.  But yes, when you go to the
>>> CI server it will say it isn't secure because it isn't.  Folks are taking
>>> chances using our nightly builds anyway.  Anyone who is concerned about the
>>> risk can build from sources.
>>>
>>> My 2 cents,
>>> -Alex
>>>
>>> On 12/10/18, 8:27 AM, "Carlos Rovira"  wrote:
>>>
>>> thanks Josh for looking this issue
>>>
>>> I think we can't remove the https, since all the site is secure and
>>> we need
>>> to enforce this to avoid problems with google.
>>> You should we change to http?
>>>
>>> Any suggestions are welcome
>>>
>>> thanks
>>>
>>>
>>>
>>>
>>> El lun., 10 dic. 2018 a las 16:55, Josh Tynjala (<
>>> joshtynj...@apache.org>)
>>> escribió:
>>>
>>> > Yeah, it's been like that for a while. This is the error that I
>>> see in
>>> > Firefox:
>>> >
>>> > Secure Connection Failed
>>> >
>>> > An error occurred during a connection to
>>> > apacheroyaleci.westus2.cloudapp.azure.com:8080. SSL received a
>>> record
>>> > that exceeded the maximum permissible length. Error code:
>>> > SSL_ERROR_RX_RECORD_TOO_LONG
>>> >
>>> > I guess that means that something is wrong with how the
>>> certificate is set
>>> > up.
>>> >
>>> > I've found that the links work if you change them from https to
>>> http.
>>> >
>>> > - Josh
>>> >
>>> > On 2018/12/10 14:44:06, Carlos Rovira 
>>> wrote:
>>> > > Hi,
>>> > >
>>> > > I'm updating the site, and I'm finding this tow links are not
>>> working:
>>> > >
>>> > > royale-asjs artifacts
>>> > > <
>>> >
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuild%2Fartifact%2Fout%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=5r4MtCUBRO1yb%2FxhlW2nTM4a%2F4PxQd1b9KftLLQCPqA%3D&reserved=0
>>> > >
>>> > > royale-asjs-jsonly artifacts
>>> > > <
>>> >
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=yPc%2B6Rv7h7xO00RB0nvQTzuMdKJbeigK5MmU4brffy0%3D&reserved=0
>>> > >
>>> > >
>>> > > (those are located at the end of download page, in pre-site the
>>> link is:
>>> > >
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fdownload%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=CYN40RLz2nXpS7gTBHfuZCSSq6M1rMFLJWksiSGll1U%3D&reserved=0
>>> )
>>> > >
>>> > > I'll continue updating things, if someone can let me know about
>>> this
>>> > before
>>> > > publish that will be great
>>> > >
>>> > > thanks!
>>> > >
>>> > >
>>> > >
>>> > > El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira (<
>>> > carlosrov...@apache.org>)
>>> > > escribió:
>>> > >
>>> > > > Thanks Piotr,
>>> > > >
>>> > > > I'll do this on Monday evening
>>> > > >
>>> > > > thanks
>>> > > >
>>> > > > Carlos
>>> > > >
>>> > > >
>>> > > > El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
>>> > > > piotrzarzyck...@gmail.com>) escribió:
>>>   

Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-11 Thread Carlos Rovira
Hi all

updates to the website are live. Although I saw there's still some few
little issues, that I'll solve more later since I must to left right now.

I added Jewel Example as "Tour de Jewel" in "Home" and "Feature" pages, so
this points to: http://royale.apache.org/tourdejewel/

More to share in a few hours.

:)

Carlos








El lun., 10 dic. 2018 a las 18:30, Carlos Rovira (<
carlos.rov...@codeoscopic.com>) escribió:

> Ok Alex,
>
> I'll change the 2 links to http for now. Maybe it should make a difference
> with browsers and google. If we have some problems we can check later.
>
> I'll wait an hour or so if someone want to make some other change before
> publish.
>
> thanks!
>
> Carlos
>
>
>
>
>
>
> El lun., 10 dic. 2018 a las 18:15, Alex Harui ()
> escribió:
>
>> Hopefully the links to the CI server are not for release artifacts, but
>> just nightly builds.
>>
>> If someone wants to pay for an HTTPS cert for our CI server, please do so
>> and set it up.
>>
>> Otherwise, those links will have to be HTTP.  I don't see from a quick
>> internet search that having a link to HTTP on a page will mean that the
>> page containing the link is marked insecure.  But yes, when you go to the
>> CI server it will say it isn't secure because it isn't.  Folks are taking
>> chances using our nightly builds anyway.  Anyone who is concerned about the
>> risk can build from sources.
>>
>> My 2 cents,
>> -Alex
>>
>> On 12/10/18, 8:27 AM, "Carlos Rovira"  wrote:
>>
>> thanks Josh for looking this issue
>>
>> I think we can't remove the https, since all the site is secure and
>> we need
>> to enforce this to avoid problems with google.
>> You should we change to http?
>>
>> Any suggestions are welcome
>>
>> thanks
>>
>>
>>
>>
>> El lun., 10 dic. 2018 a las 16:55, Josh Tynjala (<
>> joshtynj...@apache.org>)
>> escribió:
>>
>> > Yeah, it's been like that for a while. This is the error that I see
>> in
>> > Firefox:
>> >
>> > Secure Connection Failed
>> >
>> > An error occurred during a connection to
>> > apacheroyaleci.westus2.cloudapp.azure.com:8080. SSL received a
>> record
>> > that exceeded the maximum permissible length. Error code:
>> > SSL_ERROR_RX_RECORD_TOO_LONG
>> >
>> > I guess that means that something is wrong with how the certificate
>> is set
>> > up.
>> >
>> > I've found that the links work if you change them from https to
>> http.
>> >
>> > - Josh
>> >
>> > On 2018/12/10 14:44:06, Carlos Rovira 
>> wrote:
>> > > Hi,
>> > >
>> > > I'm updating the site, and I'm finding this tow links are not
>> working:
>> > >
>> > > royale-asjs artifacts
>> > > <
>> >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuild%2Fartifact%2Fout%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=5r4MtCUBRO1yb%2FxhlW2nTM4a%2F4PxQd1b9KftLLQCPqA%3D&reserved=0
>> > >
>> > > royale-asjs-jsonly artifacts
>> > > <
>> >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=yPc%2B6Rv7h7xO00RB0nvQTzuMdKJbeigK5MmU4brffy0%3D&reserved=0
>> > >
>> > >
>> > > (those are located at the end of download page, in pre-site the
>> link is:
>> > >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fdownload%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=CYN40RLz2nXpS7gTBHfuZCSSq6M1rMFLJWksiSGll1U%3D&reserved=0
>> )
>> > >
>> > > I'll continue updating things, if someone can let me know about
>> this
>> > before
>> > > publish that will be great
>> > >
>> > > thanks!
>> > >
>> > >
>> > >
>> > > El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira (<
>> > carlosrov...@apache.org>)
>> > > escribió:
>> > >
>> > > > Thanks Piotr,
>> > > >
>> > > > I'll do this on Monday evening
>> > > >
>> > > > thanks
>> > > >
>> > > > Carlos
>> > > >
>> > > >
>> > > > El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
>> > > > piotrzarzyck...@gmail.com>) escribió:
>> > > >
>> > > >> Hi Guys,
>> > > >>
>> > > >> I just published release [1]. Can someone update information on
>> > website ?
>> > > >>
>> > > >> [1]
>> > > >>
>> >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Fapache-royale-0.9.4&data=02%7C01%7Caharui%40adobe

Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-10 Thread Carlos Rovira
Ok Alex,

I'll change the 2 links to http for now. Maybe it should make a difference
with browsers and google. If we have some problems we can check later.

I'll wait an hour or so if someone want to make some other change before
publish.

thanks!

Carlos






El lun., 10 dic. 2018 a las 18:15, Alex Harui ()
escribió:

> Hopefully the links to the CI server are not for release artifacts, but
> just nightly builds.
>
> If someone wants to pay for an HTTPS cert for our CI server, please do so
> and set it up.
>
> Otherwise, those links will have to be HTTP.  I don't see from a quick
> internet search that having a link to HTTP on a page will mean that the
> page containing the link is marked insecure.  But yes, when you go to the
> CI server it will say it isn't secure because it isn't.  Folks are taking
> chances using our nightly builds anyway.  Anyone who is concerned about the
> risk can build from sources.
>
> My 2 cents,
> -Alex
>
> On 12/10/18, 8:27 AM, "Carlos Rovira"  wrote:
>
> thanks Josh for looking this issue
>
> I think we can't remove the https, since all the site is secure and we
> need
> to enforce this to avoid problems with google.
> You should we change to http?
>
> Any suggestions are welcome
>
> thanks
>
>
>
>
> El lun., 10 dic. 2018 a las 16:55, Josh Tynjala (<
> joshtynj...@apache.org>)
> escribió:
>
> > Yeah, it's been like that for a while. This is the error that I see
> in
> > Firefox:
> >
> > Secure Connection Failed
> >
> > An error occurred during a connection to
> > apacheroyaleci.westus2.cloudapp.azure.com:8080. SSL received a
> record
> > that exceeded the maximum permissible length. Error code:
> > SSL_ERROR_RX_RECORD_TOO_LONG
> >
> > I guess that means that something is wrong with how the certificate
> is set
> > up.
> >
> > I've found that the links work if you change them from https to http.
> >
> > - Josh
> >
> > On 2018/12/10 14:44:06, Carlos Rovira 
> wrote:
> > > Hi,
> > >
> > > I'm updating the site, and I'm finding this tow links are not
> working:
> > >
> > > royale-asjs artifacts
> > > <
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuild%2Fartifact%2Fout%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=5r4MtCUBRO1yb%2FxhlW2nTM4a%2F4PxQd1b9KftLLQCPqA%3D&reserved=0
> > >
> > > royale-asjs-jsonly artifacts
> > > <
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=yPc%2B6Rv7h7xO00RB0nvQTzuMdKJbeigK5MmU4brffy0%3D&reserved=0
> > >
> > >
> > > (those are located at the end of download page, in pre-site the
> link is:
> > >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fdownload%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=CYN40RLz2nXpS7gTBHfuZCSSq6M1rMFLJWksiSGll1U%3D&reserved=0
> )
> > >
> > > I'll continue updating things, if someone can let me know about
> this
> > before
> > > publish that will be great
> > >
> > > thanks!
> > >
> > >
> > >
> > > El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira (<
> > carlosrov...@apache.org>)
> > > escribió:
> > >
> > > > Thanks Piotr,
> > > >
> > > > I'll do this on Monday evening
> > > >
> > > > thanks
> > > >
> > > > Carlos
> > > >
> > > >
> > > > El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > >> Hi Guys,
> > > >>
> > > >> I just published release [1]. Can someone update information on
> > website ?
> > > >>
> > > >> [1]
> > > >>
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Fapache-royale-0.9.4&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=VJp8FXM3MWqxUKvItIJddlAPXj8KZ3wMtXgNms5tBmg%3D&reserved=0
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >>
> > > >> śr., 5 gru 2018 o 07:53 Alex Harui 
> > napisał(a):
> > > >>
> > > >> > Hey, how about that!?  The release script failed to do the svn
> > commit
> > > >> but
> > > >> > Ant didn't fail.  I guess it was because my svn repos were
> funky. I
> > > >> never
> > > >> > thought to check dist or look 

Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-10 Thread Alex Harui
Hopefully the links to the CI server are not for release artifacts, but just 
nightly builds.

If someone wants to pay for an HTTPS cert for our CI server, please do so and 
set it up.

Otherwise, those links will have to be HTTP.  I don't see from a quick internet 
search that having a link to HTTP on a page will mean that the page containing 
the link is marked insecure.  But yes, when you go to the CI server it will say 
it isn't secure because it isn't.  Folks are taking chances using our nightly 
builds anyway.  Anyone who is concerned about the risk can build from sources.

My 2 cents,
-Alex

On 12/10/18, 8:27 AM, "Carlos Rovira"  wrote:

thanks Josh for looking this issue

I think we can't remove the https, since all the site is secure and we need
to enforce this to avoid problems with google.
You should we change to http?

Any suggestions are welcome

thanks




El lun., 10 dic. 2018 a las 16:55, Josh Tynjala ()
escribió:

> Yeah, it's been like that for a while. This is the error that I see in
> Firefox:
>
> Secure Connection Failed
>
> An error occurred during a connection to
> apacheroyaleci.westus2.cloudapp.azure.com:8080. SSL received a record
> that exceeded the maximum permissible length. Error code:
> SSL_ERROR_RX_RECORD_TOO_LONG
>
> I guess that means that something is wrong with how the certificate is set
> up.
>
> I've found that the links work if you change them from https to http.
>
> - Josh
>
> On 2018/12/10 14:44:06, Carlos Rovira  wrote:
> > Hi,
> >
> > I'm updating the site, and I'm finding this tow links are not working:
> >
> > royale-asjs artifacts
> > <
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuild%2Fartifact%2Fout%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=5r4MtCUBRO1yb%2FxhlW2nTM4a%2F4PxQd1b9KftLLQCPqA%3D&reserved=0
> >
> > royale-asjs-jsonly artifacts
> > <
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=yPc%2B6Rv7h7xO00RB0nvQTzuMdKJbeigK5MmU4brffy0%3D&reserved=0
> >
> >
> > (those are located at the end of download page, in pre-site the link is:
> > 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fdownload%2F&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=CYN40RLz2nXpS7gTBHfuZCSSq6M1rMFLJWksiSGll1U%3D&reserved=0
 )
> >
> > I'll continue updating things, if someone can let me know about this
> before
> > publish that will be great
> >
> > thanks!
> >
> >
> >
> > El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira (<
> carlosrov...@apache.org>)
> > escribió:
> >
> > > Thanks Piotr,
> > >
> > > I'll do this on Monday evening
> > >
> > > thanks
> > >
> > > Carlos
> > >
> > >
> > > El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > >> Hi Guys,
> > >>
> > >> I just published release [1]. Can someone update information on
> website ?
> > >>
> > >> [1]
> > >>
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Fapache-royale-0.9.4&data=02%7C01%7Caharui%40adobe.com%7Cc77148b9b6064e554dc108d65ebc5509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636800560316016139&sdata=VJp8FXM3MWqxUKvItIJddlAPXj8KZ3wMtXgNms5tBmg%3D&reserved=0
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> śr., 5 gru 2018 o 07:53 Alex Harui 
> napisał(a):
> > >>
> > >> > Hey, how about that!?  The release script failed to do the svn
> commit
> > >> but
> > >> > Ant didn't fail.  I guess it was because my svn repos were funky. I
> > >> never
> > >> > thought to check dist or look for commit messages.I re-ran that
> part
> > >> > and it looks like it worked this time.
> > >> >
> > >> > -Alex
> > >> >
> > >> > On 12/4/18, 3:03 AM, "Piotr Zarzycki" 
> > >> wrote:
> > >> >
> > >> > Hi Justin,
> > >> >
> > >> > Thanks for the link!
> > >> >
> > >> > Piotr
> > >> >
> > >> > wt., 4 gru 2018 o 11:45 Justin Mclean  >
> > >> > napisał(a):
> > >> >
> > >> > > Hi,
> > >> > >
> > >> > > No it’s not been published yet or

Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-10 Thread Carlos Rovira
thanks Josh for looking this issue

I think we can't remove the https, since all the site is secure and we need
to enforce this to avoid problems with google.
You should we change to http?

Any suggestions are welcome

thanks




El lun., 10 dic. 2018 a las 16:55, Josh Tynjala ()
escribió:

> Yeah, it's been like that for a while. This is the error that I see in
> Firefox:
>
> Secure Connection Failed
>
> An error occurred during a connection to
> apacheroyaleci.westus2.cloudapp.azure.com:8080. SSL received a record
> that exceeded the maximum permissible length. Error code:
> SSL_ERROR_RX_RECORD_TOO_LONG
>
> I guess that means that something is wrong with how the certificate is set
> up.
>
> I've found that the links work if you change them from https to http.
>
> - Josh
>
> On 2018/12/10 14:44:06, Carlos Rovira  wrote:
> > Hi,
> >
> > I'm updating the site, and I'm finding this tow links are not working:
> >
> > royale-asjs artifacts
> > <
> https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSuccessfulBuild/artifact/out/
> >
> > royale-asjs-jsonly artifacts
> > <
> https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/artifact/out/
> >
> >
> > (those are located at the end of download page, in pre-site the link is:
> > https://royale.codeoscopic.com/download/ )
> >
> > I'll continue updating things, if someone can let me know about this
> before
> > publish that will be great
> >
> > thanks!
> >
> >
> >
> > El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira (<
> carlosrov...@apache.org>)
> > escribió:
> >
> > > Thanks Piotr,
> > >
> > > I'll do this on Monday evening
> > >
> > > thanks
> > >
> > > Carlos
> > >
> > >
> > > El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > >> Hi Guys,
> > >>
> > >> I just published release [1]. Can someone update information on
> website ?
> > >>
> > >> [1]
> > >>
> https://github.com/apache/royale-asjs/releases/tag/apache-royale-0.9.4
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> śr., 5 gru 2018 o 07:53 Alex Harui 
> napisał(a):
> > >>
> > >> > Hey, how about that!?  The release script failed to do the svn
> commit
> > >> but
> > >> > Ant didn't fail.  I guess it was because my svn repos were funky. I
> > >> never
> > >> > thought to check dist or look for commit messages.I re-ran that
> part
> > >> > and it looks like it worked this time.
> > >> >
> > >> > -Alex
> > >> >
> > >> > On 12/4/18, 3:03 AM, "Piotr Zarzycki" 
> > >> wrote:
> > >> >
> > >> > Hi Justin,
> > >> >
> > >> > Thanks for the link!
> > >> >
> > >> > Piotr
> > >> >
> > >> > wt., 4 gru 2018 o 11:45 Justin Mclean  >
> > >> > napisał(a):
> > >> >
> > >> > > Hi,
> > >> > >
> > >> > > No it’s not been published yet or distributed to the mirrors.
> [1]
> > >> > >
> > >> > > Thanks,
> > >> > > Justin
> > >> > >
> > >> > > 1.
> > >> >
> > >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2F&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347461558&sdata=w6WVoT2ef%2B%2FfJ1NxA77%2FAUCzSoElQT95oB0AXcxTUL8%3D&reserved=0
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> >
> > >> > Piotr Zarzycki
> > >> >
> > >> > Patreon: *
> > >> >
> > >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
> > >> > <
> > >> >
> > >>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
> > >> > >*
> > >> >
> > >> >
> > >> >
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> *
> > >>
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-10 Thread Carlos Rovira
Thanks Andrew

One more thing I did just now was to change all Jewel example post removing
the reference to the future 0.9.3 and change to:

"It uses the new Jewel UI set that supports themes and is available in the 0.9.4 release or later."


El lun., 10 dic. 2018 a las 16:29, Andrew Wetmore ()
escribió:

> Hi!
>
> I have made some small edits to the announcement, and I think it is good
> to go!
>
> On Mon, Dec 10, 2018 at 11:10 AM Carlos Rovira 
> wrote:
>
>> Hi,
>>
>> since there's many changes in the website. I put here the links to review
>> before publish in r.a.o:
>>
>> * Release Post
>>
>> @Andrew Wetmore  please review I added 2 paragraphs
>> in addition to standard release post to explain better what people can find
>> in 0.9.4
>>
>> https://royale.codeoscopic.com/apache-royale-v0-9-4-released/
>>
>> * Links that are the same. Just changed links from 0.9.2 to 0.9.4
>>
>> https://royale.codeoscopic.com/download/
>> https://royale.codeoscopic.com/source-code/
>>
>> * Team Page (added Pushmina and Greg, no photos or more info for now)
>>
>> https://royale.codeoscopic.com/team/
>>
>> Let me know if you see all ok or we need to add something more
>>
>> Thanks
>>
>>
>> El lun., 10 dic. 2018 a las 15:44, Carlos Rovira (<
>> carlosrov...@apache.org>) escribió:
>>
>>> Hi,
>>>
>>> I'm updating the site, and I'm finding this tow links are not working:
>>>
>>> royale-asjs artifacts
>>> 
>>> royale-asjs-jsonly artifacts
>>> 
>>>
>>> (those are located at the end of download page, in pre-site the link is:
>>> https://royale.codeoscopic.com/download/ )
>>>
>>> I'll continue updating things, if someone can let me know about this
>>> before publish that will be great
>>>
>>> thanks!
>>>
>>>
>>>
>>> El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira (<
>>> carlosrov...@apache.org>) escribió:
>>>
 Thanks Piotr,

 I'll do this on Monday evening

 thanks

 Carlos


 El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
 piotrzarzyck...@gmail.com>) escribió:

> Hi Guys,
>
> I just published release [1]. Can someone update information on
> website ?
>
> [1]
> https://github.com/apache/royale-asjs/releases/tag/apache-royale-0.9.4
>
> Thanks,
> Piotr
>
> śr., 5 gru 2018 o 07:53 Alex Harui 
> napisał(a):
>
> > Hey, how about that!?  The release script failed to do the svn
> commit but
> > Ant didn't fail.  I guess it was because my svn repos were funky. I
> never
> > thought to check dist or look for commit messages.I re-ran that
> part
> > and it looks like it worked this time.
> >
> > -Alex
> >
> > On 12/4/18, 3:03 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Justin,
> >
> > Thanks for the link!
> >
> > Piotr
> >
> > wt., 4 gru 2018 o 11:45 Justin Mclean 
> > napisał(a):
> >
> > > Hi,
> > >
> > > No it’s not been published yet or distributed to the mirrors.
> [1]
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1.
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2F&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347461558&sdata=w6WVoT2ef%2B%2FfJ1NxA77%2FAUCzSoElQT95oB0AXcxTUL8%3D&reserved=0
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
> > <
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
> > >*
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


 --
 Carlos Rovira
 http://about.me/carlosrovira


>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-10 Thread Josh Tynjala
Yeah, it's been like that for a while. This is the error that I see in Firefox:

Secure Connection Failed

An error occurred during a connection to 
apacheroyaleci.westus2.cloudapp.azure.com:8080. SSL received a record that 
exceeded the maximum permissible length. Error code: 
SSL_ERROR_RX_RECORD_TOO_LONG 

I guess that means that something is wrong with how the certificate is set up.

I've found that the links work if you change them from https to http.

- Josh

On 2018/12/10 14:44:06, Carlos Rovira  wrote: 
> Hi,
> 
> I'm updating the site, and I'm finding this tow links are not working:
> 
> royale-asjs artifacts
> 
> royale-asjs-jsonly artifacts
> 
> 
> (those are located at the end of download page, in pre-site the link is:
> https://royale.codeoscopic.com/download/ )
> 
> I'll continue updating things, if someone can let me know about this before
> publish that will be great
> 
> thanks!
> 
> 
> 
> El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira ()
> escribió:
> 
> > Thanks Piotr,
> >
> > I'll do this on Monday evening
> >
> > thanks
> >
> > Carlos
> >
> >
> > El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Hi Guys,
> >>
> >> I just published release [1]. Can someone update information on website ?
> >>
> >> [1]
> >> https://github.com/apache/royale-asjs/releases/tag/apache-royale-0.9.4
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 5 gru 2018 o 07:53 Alex Harui  napisał(a):
> >>
> >> > Hey, how about that!?  The release script failed to do the svn commit
> >> but
> >> > Ant didn't fail.  I guess it was because my svn repos were funky. I
> >> never
> >> > thought to check dist or look for commit messages.I re-ran that part
> >> > and it looks like it worked this time.
> >> >
> >> > -Alex
> >> >
> >> > On 12/4/18, 3:03 AM, "Piotr Zarzycki" 
> >> wrote:
> >> >
> >> > Hi Justin,
> >> >
> >> > Thanks for the link!
> >> >
> >> > Piotr
> >> >
> >> > wt., 4 gru 2018 o 11:45 Justin Mclean 
> >> > napisał(a):
> >> >
> >> > > Hi,
> >> > >
> >> > > No it’s not been published yet or distributed to the mirrors. [1]
> >> > >
> >> > > Thanks,
> >> > > Justin
> >> > >
> >> > > 1.
> >> >
> >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2F&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347461558&sdata=w6WVoT2ef%2B%2FfJ1NxA77%2FAUCzSoElQT95oB0AXcxTUL8%3D&reserved=0
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Piotr Zarzycki
> >> >
> >> > Patreon: *
> >> >
> >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
> >> > <
> >> >
> >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
> >> > >*
> >> >
> >> >
> >> >
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> *
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira
> 


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-10 Thread Andrew Wetmore
Hi!

I have made some small edits to the announcement, and I think it is good to
go!

On Mon, Dec 10, 2018 at 11:10 AM Carlos Rovira 
wrote:

> Hi,
>
> since there's many changes in the website. I put here the links to review
> before publish in r.a.o:
>
> * Release Post
>
> @Andrew Wetmore  please review I added 2 paragraphs
> in addition to standard release post to explain better what people can find
> in 0.9.4
>
> https://royale.codeoscopic.com/apache-royale-v0-9-4-released/
>
> * Links that are the same. Just changed links from 0.9.2 to 0.9.4
>
> https://royale.codeoscopic.com/download/
> https://royale.codeoscopic.com/source-code/
>
> * Team Page (added Pushmina and Greg, no photos or more info for now)
>
> https://royale.codeoscopic.com/team/
>
> Let me know if you see all ok or we need to add something more
>
> Thanks
>
>
> El lun., 10 dic. 2018 a las 15:44, Carlos Rovira ()
> escribió:
>
>> Hi,
>>
>> I'm updating the site, and I'm finding this tow links are not working:
>>
>> royale-asjs artifacts
>> 
>> royale-asjs-jsonly artifacts
>> 
>>
>> (those are located at the end of download page, in pre-site the link is:
>> https://royale.codeoscopic.com/download/ )
>>
>> I'll continue updating things, if someone can let me know about this
>> before publish that will be great
>>
>> thanks!
>>
>>
>>
>> El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira ()
>> escribió:
>>
>>> Thanks Piotr,
>>>
>>> I'll do this on Monday evening
>>>
>>> thanks
>>>
>>> Carlos
>>>
>>>
>>> El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
>>> piotrzarzyck...@gmail.com>) escribió:
>>>
 Hi Guys,

 I just published release [1]. Can someone update information on website
 ?

 [1]
 https://github.com/apache/royale-asjs/releases/tag/apache-royale-0.9.4

 Thanks,
 Piotr

 śr., 5 gru 2018 o 07:53 Alex Harui 
 napisał(a):

 > Hey, how about that!?  The release script failed to do the svn commit
 but
 > Ant didn't fail.  I guess it was because my svn repos were funky. I
 never
 > thought to check dist or look for commit messages.I re-ran that
 part
 > and it looks like it worked this time.
 >
 > -Alex
 >
 > On 12/4/18, 3:03 AM, "Piotr Zarzycki" 
 wrote:
 >
 > Hi Justin,
 >
 > Thanks for the link!
 >
 > Piotr
 >
 > wt., 4 gru 2018 o 11:45 Justin Mclean 
 > napisał(a):
 >
 > > Hi,
 > >
 > > No it’s not been published yet or distributed to the mirrors.
 [1]
 > >
 > > Thanks,
 > > Justin
 > >
 > > 1.
 >
 https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2F&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347461558&sdata=w6WVoT2ef%2B%2FfJ1NxA77%2FAUCzSoElQT95oB0AXcxTUL8%3D&reserved=0
 >
 >
 >
 > --
 >
 > Piotr Zarzycki
 >
 > Patreon: *
 >
 https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
 > <
 >
 https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
 > >*
 >
 >
 >

 --

 Piotr Zarzycki

 Patreon: *https://www.patreon.com/piotrzarzycki
 *

>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>>
>>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-10 Thread Carlos Rovira
Hi,

since there's many changes in the website. I put here the links to review
before publish in r.a.o:

* Release Post

@Andrew Wetmore  please review I added 2 paragraphs in
addition to standard release post to explain better what people can find in
0.9.4

https://royale.codeoscopic.com/apache-royale-v0-9-4-released/

* Links that are the same. Just changed links from 0.9.2 to 0.9.4

https://royale.codeoscopic.com/download/
https://royale.codeoscopic.com/source-code/

* Team Page (added Pushmina and Greg, no photos or more info for now)

https://royale.codeoscopic.com/team/

Let me know if you see all ok or we need to add something more

Thanks


El lun., 10 dic. 2018 a las 15:44, Carlos Rovira ()
escribió:

> Hi,
>
> I'm updating the site, and I'm finding this tow links are not working:
>
> royale-asjs artifacts
> 
> royale-asjs-jsonly artifacts
> 
>
> (those are located at the end of download page, in pre-site the link is:
> https://royale.codeoscopic.com/download/ )
>
> I'll continue updating things, if someone can let me know about this
> before publish that will be great
>
> thanks!
>
>
>
> El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira ()
> escribió:
>
>> Thanks Piotr,
>>
>> I'll do this on Monday evening
>>
>> thanks
>>
>> Carlos
>>
>>
>> El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>>
>>> Hi Guys,
>>>
>>> I just published release [1]. Can someone update information on website ?
>>>
>>> [1]
>>> https://github.com/apache/royale-asjs/releases/tag/apache-royale-0.9.4
>>>
>>> Thanks,
>>> Piotr
>>>
>>> śr., 5 gru 2018 o 07:53 Alex Harui 
>>> napisał(a):
>>>
>>> > Hey, how about that!?  The release script failed to do the svn commit
>>> but
>>> > Ant didn't fail.  I guess it was because my svn repos were funky. I
>>> never
>>> > thought to check dist or look for commit messages.I re-ran that
>>> part
>>> > and it looks like it worked this time.
>>> >
>>> > -Alex
>>> >
>>> > On 12/4/18, 3:03 AM, "Piotr Zarzycki" 
>>> wrote:
>>> >
>>> > Hi Justin,
>>> >
>>> > Thanks for the link!
>>> >
>>> > Piotr
>>> >
>>> > wt., 4 gru 2018 o 11:45 Justin Mclean 
>>> > napisał(a):
>>> >
>>> > > Hi,
>>> > >
>>> > > No it’s not been published yet or distributed to the mirrors. [1]
>>> > >
>>> > > Thanks,
>>> > > Justin
>>> > >
>>> > > 1.
>>> >
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2F&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347461558&sdata=w6WVoT2ef%2B%2FfJ1NxA77%2FAUCzSoElQT95oB0AXcxTUL8%3D&reserved=0
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > Piotr Zarzycki
>>> >
>>> > Patreon: *
>>> >
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
>>> > <
>>> >
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
>>> > >*
>>> >
>>> >
>>> >
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> *
>>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-10 Thread Carlos Rovira
Hi,

I'm updating the site, and I'm finding this tow links are not working:

royale-asjs artifacts

royale-asjs-jsonly artifacts


(those are located at the end of download page, in pre-site the link is:
https://royale.codeoscopic.com/download/ )

I'll continue updating things, if someone can let me know about this before
publish that will be great

thanks!



El sáb., 8 dic. 2018 a las 13:00, Carlos Rovira ()
escribió:

> Thanks Piotr,
>
> I'll do this on Monday evening
>
> thanks
>
> Carlos
>
>
> El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Hi Guys,
>>
>> I just published release [1]. Can someone update information on website ?
>>
>> [1]
>> https://github.com/apache/royale-asjs/releases/tag/apache-royale-0.9.4
>>
>> Thanks,
>> Piotr
>>
>> śr., 5 gru 2018 o 07:53 Alex Harui  napisał(a):
>>
>> > Hey, how about that!?  The release script failed to do the svn commit
>> but
>> > Ant didn't fail.  I guess it was because my svn repos were funky. I
>> never
>> > thought to check dist or look for commit messages.I re-ran that part
>> > and it looks like it worked this time.
>> >
>> > -Alex
>> >
>> > On 12/4/18, 3:03 AM, "Piotr Zarzycki" 
>> wrote:
>> >
>> > Hi Justin,
>> >
>> > Thanks for the link!
>> >
>> > Piotr
>> >
>> > wt., 4 gru 2018 o 11:45 Justin Mclean 
>> > napisał(a):
>> >
>> > > Hi,
>> > >
>> > > No it’s not been published yet or distributed to the mirrors. [1]
>> > >
>> > > Thanks,
>> > > Justin
>> > >
>> > > 1.
>> >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2F&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347461558&sdata=w6WVoT2ef%2B%2FfJ1NxA77%2FAUCzSoElQT95oB0AXcxTUL8%3D&reserved=0
>> >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *
>> >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
>> > <
>> >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
>> > >*
>> >
>> >
>> >
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-08 Thread Carlos Rovira
Thanks Piotr,

I'll do this on Monday evening

thanks

Carlos


El sáb., 8 dic. 2018 a las 9:10, Piotr Zarzycki ()
escribió:

> Hi Guys,
>
> I just published release [1]. Can someone update information on website ?
>
> [1] https://github.com/apache/royale-asjs/releases/tag/apache-royale-0.9.4
>
> Thanks,
> Piotr
>
> śr., 5 gru 2018 o 07:53 Alex Harui  napisał(a):
>
> > Hey, how about that!?  The release script failed to do the svn commit but
> > Ant didn't fail.  I guess it was because my svn repos were funky. I never
> > thought to check dist or look for commit messages.I re-ran that part
> > and it looks like it worked this time.
> >
> > -Alex
> >
> > On 12/4/18, 3:03 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Justin,
> >
> > Thanks for the link!
> >
> > Piotr
> >
> > wt., 4 gru 2018 o 11:45 Justin Mclean 
> > napisał(a):
> >
> > > Hi,
> > >
> > > No it’s not been published yet or distributed to the mirrors. [1]
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1.
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2F&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347461558&sdata=w6WVoT2ef%2B%2FfJ1NxA77%2FAUCzSoElQT95oB0AXcxTUL8%3D&reserved=0
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
> > <
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
> > >*
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 
Carlos Rovira
http://about.me/carlosrovira


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-08 Thread Piotr Zarzycki
Hi Guys,

I just published release [1]. Can someone update information on website ?

[1] https://github.com/apache/royale-asjs/releases/tag/apache-royale-0.9.4

Thanks,
Piotr

śr., 5 gru 2018 o 07:53 Alex Harui  napisał(a):

> Hey, how about that!?  The release script failed to do the svn commit but
> Ant didn't fail.  I guess it was because my svn repos were funky. I never
> thought to check dist or look for commit messages.I re-ran that part
> and it looks like it worked this time.
>
> -Alex
>
> On 12/4/18, 3:03 AM, "Piotr Zarzycki"  wrote:
>
> Hi Justin,
>
> Thanks for the link!
>
> Piotr
>
> wt., 4 gru 2018 o 11:45 Justin Mclean 
> napisał(a):
>
> > Hi,
> >
> > No it’s not been published yet or distributed to the mirrors. [1]
> >
> > Thanks,
> > Justin
> >
> > 1.
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2F&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347461558&sdata=w6WVoT2ef%2B%2FfJ1NxA77%2FAUCzSoElQT95oB0AXcxTUL8%3D&reserved=0
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0
> >*
>
>
>

-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-04 Thread Alex Harui
Hey, how about that!?  The release script failed to do the svn commit but Ant 
didn't fail.  I guess it was because my svn repos were funky. I never thought 
to check dist or look for commit messages.I re-ran that part and it looks 
like it worked this time.

-Alex

On 12/4/18, 3:03 AM, "Piotr Zarzycki"  wrote:

Hi Justin,

Thanks for the link!

Piotr

wt., 4 gru 2018 o 11:45 Justin Mclean  napisał(a):

> Hi,
>
> No it’s not been published yet or distributed to the mirrors. [1]
>
> Thanks,
> Justin
>
> 1. 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2F&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347461558&sdata=w6WVoT2ef%2B%2FfJ1NxA77%2FAUCzSoElQT95oB0AXcxTUL8%3D&reserved=0



-- 

Piotr Zarzycki

Patreon: 
*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cd488a5aaad1e432a3d3008d659d82c63%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795182347471567&sdata=gMLzMcP0a51kp%2BvQdNJUKR6Jg9IY77ysqygceehK3t4%3D&reserved=0

*




Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-04 Thread Piotr Zarzycki
Hi Justin,

Thanks for the link!

Piotr

wt., 4 gru 2018 o 11:45 Justin Mclean  napisał(a):

> Hi,
>
> No it’s not been published yet or distributed to the mirrors. [1]
>
> Thanks,
> Justin
>
> 1. https://dist.apache.org/repos/dist/release/royale/



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*


Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-04 Thread Justin Mclean
Hi,

No it’s not been published yet or distributed to the mirrors. [1]

Thanks,
Justin

1. https://dist.apache.org/repos/dist/release/royale/

Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-04 Thread Piotr Zarzycki
Hi Carlos,

I'm updating that part mostly, but I always do this once it's landed in
Apache Mirrors. I'm asking about whether it's pushed to mirrors.

Thanks, Piotr

wt., 4 gru 2018 o 11:10 Carlos Rovira  napisał(a):

> Hi Piotr,
>
> don't see in GitHub page: https://github.com/apache/royale-asjs/releases
>
> I'm waiting to publish in web and social networks, let me know when is
> update, although maybe I can't do that until weekend
>
> thanks
>
>
> El mar., 4 dic. 2018 a las 10:08, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Hi Guys,
> >
> > Was that published  ?
> >
> > Thanks,
> > Piotr
> >
> > czw., 22 lis 2018 o 09:42 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > >
> > > maybe is time to publish release and make announcement?.
> > > Let me know when that's done so I can work on update website with all
> the
> > > new info
> > >
> > > thanks
> > >
> > >
> > >
> > > El mar., 20 nov. 2018 a las 9:24, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>)
> > > escribió:
> > >
> > > > Hi Alex,
> > > >
> > > > Once artifacts will be propagated I will prepare release page on
> > GitHub.
> > > >
> > > > Piotr
> > > >
> > > > pon., 19 lis 2018 o 09:34 Alex Harui 
> > > > napisał(a):
> > > >
> > > > > Forgot to change subject.
> > > > >
> > > > > On 11/19/18, 12:00 AM, "Alex Harui" 
> > wrote:
> > > > >
> > > > > Vote passed.
> > > > >
> > > > > Artifacts have been pushed, but it looks like NPM again has the
> > > wrong
> > > > > version number.
> > > > >
> > > > > -Alex
> > > > >
> > > > > On 11/14/18, 10:46 AM, "Alex Harui" 
> > wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > This is vote for the 0.9.4 release of Apache Royale.
> > > > >
> > > > > The release candidate can be found here;
> > > > >
> > > > >
> > > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2F&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=rEjjVXYnRmmQqMQ4dO8OghvkezVUGKk%2B2goJSDbRjLk%3D&reserved=0
> > > > >
> > > > > Before voting please review the section,'What are the ASF
> > > > > requirements on
> > > > > approving a release?', at:
> > > > >
> > > > >
> > > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-release&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=ZaqI%2BBWmkzpWIEKUL5jJJwyk%2FJRIxzFwqun26JujS%2BU%3D&reserved=0
> > > > >
> > > > > 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 cross-compile a simple example
> > using
> > > > > the SDK.
> > > > >
> > > > > 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
> > > > > -royale package and use Apache Ant to run the
> > InstallAdobeSDKs
> > > > > script via:
> > > > >   ant -f InstallAdobeSDKs.xml
> > > > >
> > > > > You may also get the binary packages via NPM.  The -js
> > package
> > > > can
> > > > > be
> > > > > installed via:
> > > > >
> > > > > npm install
> > > > >
> > > > >
> > > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-roya&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=TV4GdmHvC0jQGWCnaO3ywb304roQ89yMcazgLNHs0Vc%3D&reserved=0
> > > > > le-0.9.4-bin-js.tar.gz -g
> > > > >
> > > > > The full package with SWF support can be installed via:
> > > > >
> > > > > npm install
> > > > >
> > > > >
> > > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=o%2FGD9eghAs22UKDbEPD7OyS9aqsE%2FndubZtALZN%2B2kE%3D&reserved=0{rc}/binaries/apache-r
> 

Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-04 Thread Carlos Rovira
Hi Piotr,

don't see in GitHub page: https://github.com/apache/royale-asjs/releases

I'm waiting to publish in web and social networks, let me know when is
update, although maybe I can't do that until weekend

thanks


El mar., 4 dic. 2018 a las 10:08, Piotr Zarzycki ()
escribió:

> Hi Guys,
>
> Was that published  ?
>
> Thanks,
> Piotr
>
> czw., 22 lis 2018 o 09:42 Carlos Rovira 
> napisał(a):
>
> > Hi,
> >
> > maybe is time to publish release and make announcement?.
> > Let me know when that's done so I can work on update website with all the
> > new info
> >
> > thanks
> >
> >
> >
> > El mar., 20 nov. 2018 a las 9:24, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>)
> > escribió:
> >
> > > Hi Alex,
> > >
> > > Once artifacts will be propagated I will prepare release page on
> GitHub.
> > >
> > > Piotr
> > >
> > > pon., 19 lis 2018 o 09:34 Alex Harui 
> > > napisał(a):
> > >
> > > > Forgot to change subject.
> > > >
> > > > On 11/19/18, 12:00 AM, "Alex Harui" 
> wrote:
> > > >
> > > > Vote passed.
> > > >
> > > > Artifacts have been pushed, but it looks like NPM again has the
> > wrong
> > > > version number.
> > > >
> > > > -Alex
> > > >
> > > > On 11/14/18, 10:46 AM, "Alex Harui" 
> wrote:
> > > >
> > > > Hi,
> > > >
> > > > This is vote for the 0.9.4 release of Apache Royale.
> > > >
> > > > The release candidate can be found here;
> > > >
> > > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2F&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=rEjjVXYnRmmQqMQ4dO8OghvkezVUGKk%2B2goJSDbRjLk%3D&reserved=0
> > > >
> > > > Before voting please review the section,'What are the ASF
> > > > requirements on
> > > > approving a release?', at:
> > > >
> > > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-release&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=ZaqI%2BBWmkzpWIEKUL5jJJwyk%2FJRIxzFwqun26JujS%2BU%3D&reserved=0
> > > >
> > > > 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 cross-compile a simple example
> using
> > > > the SDK.
> > > >
> > > > 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
> > > > -royale package and use Apache Ant to run the
> InstallAdobeSDKs
> > > > script via:
> > > >   ant -f InstallAdobeSDKs.xml
> > > >
> > > > You may also get the binary packages via NPM.  The -js
> package
> > > can
> > > > be
> > > > installed via:
> > > >
> > > > npm install
> > > >
> > > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-roya&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=TV4GdmHvC0jQGWCnaO3ywb304roQ89yMcazgLNHs0Vc%3D&reserved=0
> > > > le-0.9.4-bin-js.tar.gz -g
> > > >
> > > > The full package with SWF support can be installed via:
> > > >
> > > > npm install
> > > >
> > > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=o%2FGD9eghAs22UKDbEPD7OyS9aqsE%2FndubZtALZN%2B2kE%3D&reserved=0{rc}/binaries/apache-r
> 
> > <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=o%2FGD9eghAs22UKDbEPD7OyS9aqsE%2FndubZtALZN%2B2kE%3D&reserved=0%7Brc%7D/binaries/apache-r
> >
> > > <
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fro

Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-12-04 Thread Piotr Zarzycki
Hi Guys,

Was that published  ?

Thanks,
Piotr

czw., 22 lis 2018 o 09:42 Carlos Rovira 
napisał(a):

> Hi,
>
> maybe is time to publish release and make announcement?.
> Let me know when that's done so I can work on update website with all the
> new info
>
> thanks
>
>
>
> El mar., 20 nov. 2018 a las 9:24, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Hi Alex,
> >
> > Once artifacts will be propagated I will prepare release page on GitHub.
> >
> > Piotr
> >
> > pon., 19 lis 2018 o 09:34 Alex Harui 
> > napisał(a):
> >
> > > Forgot to change subject.
> > >
> > > On 11/19/18, 12:00 AM, "Alex Harui"  wrote:
> > >
> > > Vote passed.
> > >
> > > Artifacts have been pushed, but it looks like NPM again has the
> wrong
> > > version number.
> > >
> > > -Alex
> > >
> > > On 11/14/18, 10:46 AM, "Alex Harui"  wrote:
> > >
> > > Hi,
> > >
> > > This is vote for the 0.9.4 release of Apache Royale.
> > >
> > > The release candidate can be found here;
> > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2F&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=rEjjVXYnRmmQqMQ4dO8OghvkezVUGKk%2B2goJSDbRjLk%3D&reserved=0
> > >
> > > Before voting please review the section,'What are the ASF
> > > requirements on
> > > approving a release?', at:
> > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-release&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=ZaqI%2BBWmkzpWIEKUL5jJJwyk%2FJRIxzFwqun26JujS%2BU%3D&reserved=0
> > >
> > > 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 cross-compile a simple example using
> > > the SDK.
> > >
> > > 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
> > > -royale package and use Apache Ant to run the InstallAdobeSDKs
> > > script via:
> > >   ant -f InstallAdobeSDKs.xml
> > >
> > > You may also get the binary packages via NPM.  The -js package
> > can
> > > be
> > > installed via:
> > >
> > > npm install
> > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-roya&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=TV4GdmHvC0jQGWCnaO3ywb304roQ89yMcazgLNHs0Vc%3D&reserved=0
> > > le-0.9.4-bin-js.tar.gz -g
> > >
> > > The full package with SWF support can be installed via:
> > >
> > > npm install
> > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=o%2FGD9eghAs22UKDbEPD7OyS9aqsE%2FndubZtALZN%2B2kE%3D&reserved=0{rc}/binaries/apache-r
> 
> > <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=o%2FGD9eghAs22UKDbEPD7OyS9aqsE%2FndubZtALZN%2B2kE%3D&reserved=0%7Brc%7D/binaries/apache-r
> >
> > > <
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=o%2FGD9eghAs22UKDbEPD7OyS9aqsE%2FndubZtALZN%2B2kE%3D&reserved=0%7Brc%7D/binaries/apache-r
> > >
> > > oyale-0.9.4-bin-js-swf.tar.gz -g
> > >
> > > Maven artifacts are staged here:
> > >
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1025&

Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-26 Thread Alex Harui
I have updated the version numbers in the develop branches to 0.9.6.

-Alex

On 11/20/18, 12:03 AM, "OmPrakash Muppirala"  wrote:

On Mon, Nov 19, 2018 at 3:19 PM Alex Harui  wrote:

> IMO, we should just go with 0.9.6. That way we can continue to test the
> release scripts.
>

+1


>
> -Alex
>
> On 11/19/18, 3:17 PM, "Josh Tynjala"  wrote:
>
> You probably don't want to use 0.9.5@next. The @ sign denotes a "tag"
> in the npm registry, and users would need to install that particular
> version of Royale like this:
>
> npm install -g @apache-royale/royale-js@next
>
> Instead of this:
>
> npm install -g @apache-royale/royale-js
>
> You may be able to use 0.9.5-next. Technically, in semver, the dash is
> supposed to be used for prerelease builds, but I don't think that it's
> enforced. This should still be considered a different version number than
> 0.9.5, I think, and no special install command is required.
>
> - Josh
>
> On 2018/11/19 19:50:26, OmPrakash Muppirala 
> wrote:
> > Okay, I unpublished 0.9.5 and published 0.9.4.  Looks like we are
> okay for
> > now.  (It wouldn't let me publish 0.9.4 because 0.9.5 was already
> there)
> >
> > I suggest that for the next release, we can choose to skip 0.9.5 or
> for NPM
> > alone, we publish it as 0.9.5@next (or something like that)
> >
> > Thanks,
> > Om
> >
> > On Mon, Nov 19, 2018 at 11:36 AM Alex Harui 
 >
> > wrote:
> >
> > > IMO, if we aren't going to use 0.9.5, no need to unpublish it, 
just
> > > publish a 0.9.4 for now and we'll skip 0.9.5
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 11/19/18, 10:57 AM, "OmPrakash Muppirala"  >
> > > wrote:
> > >
> > > Turns out we can unpublish a version within 72 hours.  Let me
> try to
> > > unpublish 0.9.5 and publish 0.9.4 if that is possible.
> > > Although we still may not be able to publish 0.9.5 next time
> as per the
> > > docs here:
> > >
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.npmjs.com%2Fcli%2Funpublish&data=02%7C01%7Caharui%40adobe.com%7Cf44797064ab0424ed7c508d64ebea1ae%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782977998420041&sdata=hWtM%2BIRIeeu4QvMZrYovCyvDysgsW3r2sUyqoDJFeig%3D&reserved=0
> > >
> > > Thanks,
> > > Om
> > >
> > > On Mon, Nov 19, 2018 at 9:34 AM Alex Harui
> 
> > > wrote:
> > >
> > > > In the past discussion, I suggested a change to the release
> script
> > > that
> > > > apparently never happened and I did not check to see that it
> > > happened.  I
> > > > have made the suggested change and we'll see if that change
> helps on
> > > the
> > > > next release.
> > > >
> > > > I think someone could also publish the bits as 0.9.4 if they
> have
> > > time.  I
> > > > don't want to take the time to do that.  I will bump the dev
> > > branches to
> > > > 0.9.6 this week sometime.  Our next release will have to be
> 0.9.6,
> > > just
> > > > like we skipped 0.9.3.
> > > >
> > > > -Alex
> > > >
> > > > On 11/19/18, 7:25 AM, "OmPrakash Muppirala" <
> bigosma...@gmail.com>
> > > wrote:
> > > >
> > > > Yeah, there is no way to unpublish it.
> > > > I'm guessing that the the version number get bumped
> twice?
> > > >
> > > > On Mon, Nov 19, 2018 at 2:18 AM Harbs <
> harbs.li...@gmail.com>
> > > wrote:
> > > >
> > > > > Ouch. Am I correct in assuming that there’s no way to
> > > “unpublish”
> > > > 0.9.5?
> > > > >
> > > > > Why did this happen again?
> > > > >
> > > > > Harbs
> > > > >
> > > > > > On Nov 19, 2018, at 2:54 AM, Alex Harui
> > > 
> > > > > wrote:
> > > > > >
> > > > > > Artifacts have been pushed, but it looks like NPM
> again has
> > > the
> > > > wrong
> > > > > version number.
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
>
>
>




Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-11-22 Thread Carlos Rovira
Hi,

maybe is time to publish release and make announcement?.
Let me know when that's done so I can work on update website with all the
new info

thanks



El mar., 20 nov. 2018 a las 9:24, Piotr Zarzycki ()
escribió:

> Hi Alex,
>
> Once artifacts will be propagated I will prepare release page on GitHub.
>
> Piotr
>
> pon., 19 lis 2018 o 09:34 Alex Harui 
> napisał(a):
>
> > Forgot to change subject.
> >
> > On 11/19/18, 12:00 AM, "Alex Harui"  wrote:
> >
> > Vote passed.
> >
> > Artifacts have been pushed, but it looks like NPM again has the wrong
> > version number.
> >
> > -Alex
> >
> > On 11/14/18, 10:46 AM, "Alex Harui"  wrote:
> >
> > Hi,
> >
> > This is vote for the 0.9.4 release of Apache Royale.
> >
> > The release candidate can be found here;
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2F&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=rEjjVXYnRmmQqMQ4dO8OghvkezVUGKk%2B2goJSDbRjLk%3D&reserved=0
> >
> > Before voting please review the section,'What are the ASF
> > requirements on
> > approving a release?', at:
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-release&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=ZaqI%2BBWmkzpWIEKUL5jJJwyk%2FJRIxzFwqun26JujS%2BU%3D&reserved=0
> >
> > 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 cross-compile a simple example using
> > the SDK.
> >
> > 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
> > -royale package and use Apache Ant to run the InstallAdobeSDKs
> > script via:
> >   ant -f InstallAdobeSDKs.xml
> >
> > You may also get the binary packages via NPM.  The -js package
> can
> > be
> > installed via:
> >
> > npm install
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-roya&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=TV4GdmHvC0jQGWCnaO3ywb304roQ89yMcazgLNHs0Vc%3D&reserved=0
> > le-0.9.4-bin-js.tar.gz -g
> >
> > The full package with SWF support can be installed via:
> >
> > npm install
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=o%2FGD9eghAs22UKDbEPD7OyS9aqsE%2FndubZtALZN%2B2kE%3D&reserved=0{rc}/binaries/apache-r
> 
> > <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=o%2FGD9eghAs22UKDbEPD7OyS9aqsE%2FndubZtALZN%2B2kE%3D&reserved=0%7Brc%7D/binaries/apache-r
> >
> > oyale-0.9.4-bin-js-swf.tar.gz -g
> >
> > Maven artifacts are staged here:
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1025&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=59Hj17ahave9zJfjapOBE8cG6%2F8dX%2BQrqPNi4CywV3I%3D&reserved=0
> >
> > 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 I expect there
> >   

Re: [RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-11-20 Thread Piotr Zarzycki
Hi Alex,

Once artifacts will be propagated I will prepare release page on GitHub.

Piotr

pon., 19 lis 2018 o 09:34 Alex Harui  napisał(a):

> Forgot to change subject.
>
> On 11/19/18, 12:00 AM, "Alex Harui"  wrote:
>
> Vote passed.
>
> Artifacts have been pushed, but it looks like NPM again has the wrong
> version number.
>
> -Alex
>
> On 11/14/18, 10:46 AM, "Alex Harui"  wrote:
>
> Hi,
>
> This is vote for the 0.9.4 release of Apache Royale.
>
> The release candidate can be found here;
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2F&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=rEjjVXYnRmmQqMQ4dO8OghvkezVUGKk%2B2goJSDbRjLk%3D&reserved=0
>
> Before voting please review the section,'What are the ASF
> requirements on
> approving a release?', at:
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-release&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=ZaqI%2BBWmkzpWIEKUL5jJJwyk%2FJRIxzFwqun26JujS%2BU%3D&reserved=0
>
> 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 cross-compile a simple example using
> the SDK.
>
> 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
> -royale package and use Apache Ant to run the InstallAdobeSDKs
> script via:
>   ant -f InstallAdobeSDKs.xml
>
> You may also get the binary packages via NPM.  The -js package can
> be
> installed via:
>
> npm install
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-roya&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=TV4GdmHvC0jQGWCnaO3ywb304roQ89yMcazgLNHs0Vc%3D&reserved=0
> le-0.9.4-bin-js.tar.gz -g
>
> The full package with SWF support can be installed via:
>
> npm install
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=o%2FGD9eghAs22UKDbEPD7OyS9aqsE%2FndubZtALZN%2B2kE%3D&reserved=0{rc}/binaries/apache-r
> 
> oyale-0.9.4-bin-js-swf.tar.gz -g
>
> Maven artifacts are staged here:
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1025&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=59Hj17ahave9zJfjapOBE8cG6%2F8dX%2BQrqPNi4CywV3I%3D&reserved=0
>
> 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 I 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, unzipp

Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-20 Thread OmPrakash Muppirala
On Mon, Nov 19, 2018 at 3:19 PM Alex Harui  wrote:

> IMO, we should just go with 0.9.6. That way we can continue to test the
> release scripts.
>

+1


>
> -Alex
>
> On 11/19/18, 3:17 PM, "Josh Tynjala"  wrote:
>
> You probably don't want to use 0.9.5@next. The @ sign denotes a "tag"
> in the npm registry, and users would need to install that particular
> version of Royale like this:
>
> npm install -g @apache-royale/royale-js@next
>
> Instead of this:
>
> npm install -g @apache-royale/royale-js
>
> You may be able to use 0.9.5-next. Technically, in semver, the dash is
> supposed to be used for prerelease builds, but I don't think that it's
> enforced. This should still be considered a different version number than
> 0.9.5, I think, and no special install command is required.
>
> - Josh
>
> On 2018/11/19 19:50:26, OmPrakash Muppirala 
> wrote:
> > Okay, I unpublished 0.9.5 and published 0.9.4.  Looks like we are
> okay for
> > now.  (It wouldn't let me publish 0.9.4 because 0.9.5 was already
> there)
> >
> > I suggest that for the next release, we can choose to skip 0.9.5 or
> for NPM
> > alone, we publish it as 0.9.5@next (or something like that)
> >
> > Thanks,
> > Om
> >
> > On Mon, Nov 19, 2018 at 11:36 AM Alex Harui  >
> > wrote:
> >
> > > IMO, if we aren't going to use 0.9.5, no need to unpublish it, just
> > > publish a 0.9.4 for now and we'll skip 0.9.5
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 11/19/18, 10:57 AM, "OmPrakash Muppirala"  >
> > > wrote:
> > >
> > > Turns out we can unpublish a version within 72 hours.  Let me
> try to
> > > unpublish 0.9.5 and publish 0.9.4 if that is possible.
> > > Although we still may not be able to publish 0.9.5 next time
> as per the
> > > docs here:
> > >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.npmjs.com%2Fcli%2Funpublish&data=02%7C01%7Caharui%40adobe.com%7Ce0a228debe684196045a08d64e753902%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782662705454521&sdata=Clg7YGqIGCNjlYxh00ZJH5356ZnVufWGaZhQjyXqmiI%3D&reserved=0
> > >
> > > Thanks,
> > > Om
> > >
> > > On Mon, Nov 19, 2018 at 9:34 AM Alex Harui
> 
> > > wrote:
> > >
> > > > In the past discussion, I suggested a change to the release
> script
> > > that
> > > > apparently never happened and I did not check to see that it
> > > happened.  I
> > > > have made the suggested change and we'll see if that change
> helps on
> > > the
> > > > next release.
> > > >
> > > > I think someone could also publish the bits as 0.9.4 if they
> have
> > > time.  I
> > > > don't want to take the time to do that.  I will bump the dev
> > > branches to
> > > > 0.9.6 this week sometime.  Our next release will have to be
> 0.9.6,
> > > just
> > > > like we skipped 0.9.3.
> > > >
> > > > -Alex
> > > >
> > > > On 11/19/18, 7:25 AM, "OmPrakash Muppirala" <
> bigosma...@gmail.com>
> > > wrote:
> > > >
> > > > Yeah, there is no way to unpublish it.
> > > > I'm guessing that the the version number get bumped
> twice?
> > > >
> > > > On Mon, Nov 19, 2018 at 2:18 AM Harbs <
> harbs.li...@gmail.com>
> > > wrote:
> > > >
> > > > > Ouch. Am I correct in assuming that there’s no way to
> > > “unpublish”
> > > > 0.9.5?
> > > > >
> > > > > Why did this happen again?
> > > > >
> > > > > Harbs
> > > > >
> > > > > > On Nov 19, 2018, at 2:54 AM, Alex Harui
> > > 
> > > > > wrote:
> > > > > >
> > > > > > Artifacts have been pushed, but it looks like NPM
> again has
> > > the
> > > > wrong
> > > > > version number.
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
>
>
>


Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-20 Thread OmPrakash Muppirala
On Mon, Nov 19, 2018 at 3:17 PM Josh Tynjala  wrote:

> You probably don't want to use 0.9.5@next. The @ sign denotes a "tag" in
> the npm registry, and users would need to install that particular version
> of Royale like this:
>
> npm install -g @apache-royale/royale-js@next
>
> Instead of this:
>
> npm install -g @apache-royale/royale-js
>
> You may be able to use 0.9.5-next. Technically, in semver, the dash is
> supposed to be used for prerelease builds, but I don't think that it's
> enforced. This should still be considered a different version number than
> 0.9.5, I think, and no special install command is required.
>
>
You are right, that makes sense!


> - Josh
>
> On 2018/11/19 19:50:26, OmPrakash Muppirala  wrote:
> > Okay, I unpublished 0.9.5 and published 0.9.4.  Looks like we are okay
> for
> > now.  (It wouldn't let me publish 0.9.4 because 0.9.5 was already there)
> >
> > I suggest that for the next release, we can choose to skip 0.9.5 or for
> NPM
> > alone, we publish it as 0.9.5@next (or something like that)
> >
> > Thanks,
> > Om
> >
> > On Mon, Nov 19, 2018 at 11:36 AM Alex Harui 
> > wrote:
> >
> > > IMO, if we aren't going to use 0.9.5, no need to unpublish it, just
> > > publish a 0.9.4 for now and we'll skip 0.9.5
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 11/19/18, 10:57 AM, "OmPrakash Muppirala" 
> > > wrote:
> > >
> > > Turns out we can unpublish a version within 72 hours.  Let me try
> to
> > > unpublish 0.9.5 and publish 0.9.4 if that is possible.
> > > Although we still may not be able to publish 0.9.5 next time as
> per the
> > > docs here:
> > >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.npmjs.com%2Fcli%2Funpublish&data=02%7C01%7Caharui%40adobe.com%7Cde9e6b6d5418455a3c9108d64e50e5b3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782506692307805&sdata=hRImWrDaIU7sOvZW0bxMHpaPyj9U1jGqeYdtBp%2BLe00%3D&reserved=0
> > >
> > > Thanks,
> > > Om
> > >
> > > On Mon, Nov 19, 2018 at 9:34 AM Alex Harui
> 
> > > wrote:
> > >
> > > > In the past discussion, I suggested a change to the release
> script
> > > that
> > > > apparently never happened and I did not check to see that it
> > > happened.  I
> > > > have made the suggested change and we'll see if that change
> helps on
> > > the
> > > > next release.
> > > >
> > > > I think someone could also publish the bits as 0.9.4 if they have
> > > time.  I
> > > > don't want to take the time to do that.  I will bump the dev
> > > branches to
> > > > 0.9.6 this week sometime.  Our next release will have to be
> 0.9.6,
> > > just
> > > > like we skipped 0.9.3.
> > > >
> > > > -Alex
> > > >
> > > > On 11/19/18, 7:25 AM, "OmPrakash Muppirala" <
> bigosma...@gmail.com>
> > > wrote:
> > > >
> > > > Yeah, there is no way to unpublish it.
> > > > I'm guessing that the the version number get bumped twice?
> > > >
> > > > On Mon, Nov 19, 2018 at 2:18 AM Harbs  >
> > > wrote:
> > > >
> > > > > Ouch. Am I correct in assuming that there’s no way to
> > > “unpublish”
> > > > 0.9.5?
> > > > >
> > > > > Why did this happen again?
> > > > >
> > > > > Harbs
> > > > >
> > > > > > On Nov 19, 2018, at 2:54 AM, Alex Harui
> > > 
> > > > > wrote:
> > > > > >
> > > > > > Artifacts have been pushed, but it looks like NPM again
> has
> > > the
> > > > wrong
> > > > > version number.
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
>


Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-19 Thread Alex Harui
IMO, we should just go with 0.9.6. That way we can continue to test the release 
scripts.

-Alex

On 11/19/18, 3:17 PM, "Josh Tynjala"  wrote:

You probably don't want to use 0.9.5@next. The @ sign denotes a "tag" in 
the npm registry, and users would need to install that particular version of 
Royale like this:

npm install -g @apache-royale/royale-js@next

Instead of this:

npm install -g @apache-royale/royale-js

You may be able to use 0.9.5-next. Technically, in semver, the dash is 
supposed to be used for prerelease builds, but I don't think that it's 
enforced. This should still be considered a different version number than 
0.9.5, I think, and no special install command is required.

- Josh

On 2018/11/19 19:50:26, OmPrakash Muppirala  wrote: 
> Okay, I unpublished 0.9.5 and published 0.9.4.  Looks like we are okay for
> now.  (It wouldn't let me publish 0.9.4 because 0.9.5 was already there)
> 
> I suggest that for the next release, we can choose to skip 0.9.5 or for 
NPM
> alone, we publish it as 0.9.5@next (or something like that)
> 
> Thanks,
> Om
> 
> On Mon, Nov 19, 2018 at 11:36 AM Alex Harui 
> wrote:
> 
> > IMO, if we aren't going to use 0.9.5, no need to unpublish it, just
> > publish a 0.9.4 for now and we'll skip 0.9.5
> >
> > My 2 cents,
> > -Alex
> >
> > On 11/19/18, 10:57 AM, "OmPrakash Muppirala" 
> > wrote:
> >
> > Turns out we can unpublish a version within 72 hours.  Let me try to
> > unpublish 0.9.5 and publish 0.9.4 if that is possible.
> > Although we still may not be able to publish 0.9.5 next time as per 
the
> > docs here:
> > 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.npmjs.com%2Fcli%2Funpublish&data=02%7C01%7Caharui%40adobe.com%7Ce0a228debe684196045a08d64e753902%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782662705454521&sdata=Clg7YGqIGCNjlYxh00ZJH5356ZnVufWGaZhQjyXqmiI%3D&reserved=0
> >
> > Thanks,
> > Om
> >
> > On Mon, Nov 19, 2018 at 9:34 AM Alex Harui 

> > wrote:
> >
> > > In the past discussion, I suggested a change to the release script
> > that
> > > apparently never happened and I did not check to see that it
> > happened.  I
> > > have made the suggested change and we'll see if that change helps 
on
> > the
> > > next release.
> > >
> > > I think someone could also publish the bits as 0.9.4 if they have
> > time.  I
> > > don't want to take the time to do that.  I will bump the dev
> > branches to
> > > 0.9.6 this week sometime.  Our next release will have to be 0.9.6,
> > just
> > > like we skipped 0.9.3.
> > >
> > > -Alex
> > >
> > > On 11/19/18, 7:25 AM, "OmPrakash Muppirala" 
> > wrote:
> > >
> > > Yeah, there is no way to unpublish it.
> > > I'm guessing that the the version number get bumped twice?
> > >
> > > On Mon, Nov 19, 2018 at 2:18 AM Harbs 
> > wrote:
> > >
> > > > Ouch. Am I correct in assuming that there’s no way to
> > “unpublish”
> > > 0.9.5?
> > > >
> > > > Why did this happen again?
> > > >
> > > > Harbs
> > > >
> > > > > On Nov 19, 2018, at 2:54 AM, Alex Harui
> > 
> > > > wrote:
> > > > >
> > > > > Artifacts have been pushed, but it looks like NPM again 
has
> > the
> > > wrong
> > > > version number.
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
> 




Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-19 Thread Josh Tynjala
You probably don't want to use 0.9.5@next. The @ sign denotes a "tag" in the 
npm registry, and users would need to install that particular version of Royale 
like this:

npm install -g @apache-royale/royale-js@next

Instead of this:

npm install -g @apache-royale/royale-js

You may be able to use 0.9.5-next. Technically, in semver, the dash is supposed 
to be used for prerelease builds, but I don't think that it's enforced. This 
should still be considered a different version number than 0.9.5, I think, and 
no special install command is required.

- Josh

On 2018/11/19 19:50:26, OmPrakash Muppirala  wrote: 
> Okay, I unpublished 0.9.5 and published 0.9.4.  Looks like we are okay for
> now.  (It wouldn't let me publish 0.9.4 because 0.9.5 was already there)
> 
> I suggest that for the next release, we can choose to skip 0.9.5 or for NPM
> alone, we publish it as 0.9.5@next (or something like that)
> 
> Thanks,
> Om
> 
> On Mon, Nov 19, 2018 at 11:36 AM Alex Harui 
> wrote:
> 
> > IMO, if we aren't going to use 0.9.5, no need to unpublish it, just
> > publish a 0.9.4 for now and we'll skip 0.9.5
> >
> > My 2 cents,
> > -Alex
> >
> > On 11/19/18, 10:57 AM, "OmPrakash Muppirala" 
> > wrote:
> >
> > Turns out we can unpublish a version within 72 hours.  Let me try to
> > unpublish 0.9.5 and publish 0.9.4 if that is possible.
> > Although we still may not be able to publish 0.9.5 next time as per the
> > docs here:
> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.npmjs.com%2Fcli%2Funpublish&data=02%7C01%7Caharui%40adobe.com%7Cde9e6b6d5418455a3c9108d64e50e5b3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782506692307805&sdata=hRImWrDaIU7sOvZW0bxMHpaPyj9U1jGqeYdtBp%2BLe00%3D&reserved=0
> >
> > Thanks,
> > Om
> >
> > On Mon, Nov 19, 2018 at 9:34 AM Alex Harui 
> > wrote:
> >
> > > In the past discussion, I suggested a change to the release script
> > that
> > > apparently never happened and I did not check to see that it
> > happened.  I
> > > have made the suggested change and we'll see if that change helps on
> > the
> > > next release.
> > >
> > > I think someone could also publish the bits as 0.9.4 if they have
> > time.  I
> > > don't want to take the time to do that.  I will bump the dev
> > branches to
> > > 0.9.6 this week sometime.  Our next release will have to be 0.9.6,
> > just
> > > like we skipped 0.9.3.
> > >
> > > -Alex
> > >
> > > On 11/19/18, 7:25 AM, "OmPrakash Muppirala" 
> > wrote:
> > >
> > > Yeah, there is no way to unpublish it.
> > > I'm guessing that the the version number get bumped twice?
> > >
> > > On Mon, Nov 19, 2018 at 2:18 AM Harbs 
> > wrote:
> > >
> > > > Ouch. Am I correct in assuming that there’s no way to
> > “unpublish”
> > > 0.9.5?
> > > >
> > > > Why did this happen again?
> > > >
> > > > Harbs
> > > >
> > > > > On Nov 19, 2018, at 2:54 AM, Alex Harui
> > 
> > > > wrote:
> > > > >
> > > > > Artifacts have been pushed, but it looks like NPM again has
> > the
> > > wrong
> > > > version number.
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
> 


Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-19 Thread OmPrakash Muppirala
Okay, I unpublished 0.9.5 and published 0.9.4.  Looks like we are okay for
now.  (It wouldn't let me publish 0.9.4 because 0.9.5 was already there)

I suggest that for the next release, we can choose to skip 0.9.5 or for NPM
alone, we publish it as 0.9.5@next (or something like that)

Thanks,
Om

On Mon, Nov 19, 2018 at 11:36 AM Alex Harui 
wrote:

> IMO, if we aren't going to use 0.9.5, no need to unpublish it, just
> publish a 0.9.4 for now and we'll skip 0.9.5
>
> My 2 cents,
> -Alex
>
> On 11/19/18, 10:57 AM, "OmPrakash Muppirala" 
> wrote:
>
> Turns out we can unpublish a version within 72 hours.  Let me try to
> unpublish 0.9.5 and publish 0.9.4 if that is possible.
> Although we still may not be able to publish 0.9.5 next time as per the
> docs here:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.npmjs.com%2Fcli%2Funpublish&data=02%7C01%7Caharui%40adobe.com%7Cde9e6b6d5418455a3c9108d64e50e5b3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782506692307805&sdata=hRImWrDaIU7sOvZW0bxMHpaPyj9U1jGqeYdtBp%2BLe00%3D&reserved=0
>
> Thanks,
> Om
>
> On Mon, Nov 19, 2018 at 9:34 AM Alex Harui 
> wrote:
>
> > In the past discussion, I suggested a change to the release script
> that
> > apparently never happened and I did not check to see that it
> happened.  I
> > have made the suggested change and we'll see if that change helps on
> the
> > next release.
> >
> > I think someone could also publish the bits as 0.9.4 if they have
> time.  I
> > don't want to take the time to do that.  I will bump the dev
> branches to
> > 0.9.6 this week sometime.  Our next release will have to be 0.9.6,
> just
> > like we skipped 0.9.3.
> >
> > -Alex
> >
> > On 11/19/18, 7:25 AM, "OmPrakash Muppirala" 
> wrote:
> >
> > Yeah, there is no way to unpublish it.
> > I'm guessing that the the version number get bumped twice?
> >
> > On Mon, Nov 19, 2018 at 2:18 AM Harbs 
> wrote:
> >
> > > Ouch. Am I correct in assuming that there’s no way to
> “unpublish”
> > 0.9.5?
> > >
> > > Why did this happen again?
> > >
> > > Harbs
> > >
> > > > On Nov 19, 2018, at 2:54 AM, Alex Harui
> 
> > > wrote:
> > > >
> > > > Artifacts have been pushed, but it looks like NPM again has
> the
> > wrong
> > > version number.
> > >
> > >
> >
> >
> >
>
>
>


Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-19 Thread Alex Harui
IMO, if we aren't going to use 0.9.5, no need to unpublish it, just publish a 
0.9.4 for now and we'll skip 0.9.5

My 2 cents,
-Alex

On 11/19/18, 10:57 AM, "OmPrakash Muppirala"  wrote:

Turns out we can unpublish a version within 72 hours.  Let me try to
unpublish 0.9.5 and publish 0.9.4 if that is possible.
Although we still may not be able to publish 0.9.5 next time as per the
docs here: 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.npmjs.com%2Fcli%2Funpublish&data=02%7C01%7Caharui%40adobe.com%7Cde9e6b6d5418455a3c9108d64e50e5b3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782506692307805&sdata=hRImWrDaIU7sOvZW0bxMHpaPyj9U1jGqeYdtBp%2BLe00%3D&reserved=0

Thanks,
Om

On Mon, Nov 19, 2018 at 9:34 AM Alex Harui  wrote:

> In the past discussion, I suggested a change to the release script that
> apparently never happened and I did not check to see that it happened.  I
> have made the suggested change and we'll see if that change helps on the
> next release.
>
> I think someone could also publish the bits as 0.9.4 if they have time.  I
> don't want to take the time to do that.  I will bump the dev branches to
> 0.9.6 this week sometime.  Our next release will have to be 0.9.6, just
> like we skipped 0.9.3.
>
> -Alex
>
> On 11/19/18, 7:25 AM, "OmPrakash Muppirala"  wrote:
>
> Yeah, there is no way to unpublish it.
> I'm guessing that the the version number get bumped twice?
>
> On Mon, Nov 19, 2018 at 2:18 AM Harbs  wrote:
>
> > Ouch. Am I correct in assuming that there’s no way to “unpublish”
> 0.9.5?
> >
> > Why did this happen again?
> >
> > Harbs
> >
> > > On Nov 19, 2018, at 2:54 AM, Alex Harui 
> > wrote:
> > >
> > > Artifacts have been pushed, but it looks like NPM again has the
> wrong
> > version number.
> >
> >
>
>
>




Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-19 Thread OmPrakash Muppirala
Turns out we can unpublish a version within 72 hours.  Let me try to
unpublish 0.9.5 and publish 0.9.4 if that is possible.
Although we still may not be able to publish 0.9.5 next time as per the
docs here: https://docs.npmjs.com/cli/unpublish

Thanks,
Om

On Mon, Nov 19, 2018 at 9:34 AM Alex Harui  wrote:

> In the past discussion, I suggested a change to the release script that
> apparently never happened and I did not check to see that it happened.  I
> have made the suggested change and we'll see if that change helps on the
> next release.
>
> I think someone could also publish the bits as 0.9.4 if they have time.  I
> don't want to take the time to do that.  I will bump the dev branches to
> 0.9.6 this week sometime.  Our next release will have to be 0.9.6, just
> like we skipped 0.9.3.
>
> -Alex
>
> On 11/19/18, 7:25 AM, "OmPrakash Muppirala"  wrote:
>
> Yeah, there is no way to unpublish it.
> I'm guessing that the the version number get bumped twice?
>
> On Mon, Nov 19, 2018 at 2:18 AM Harbs  wrote:
>
> > Ouch. Am I correct in assuming that there’s no way to “unpublish”
> 0.9.5?
> >
> > Why did this happen again?
> >
> > Harbs
> >
> > > On Nov 19, 2018, at 2:54 AM, Alex Harui 
> > wrote:
> > >
> > > Artifacts have been pushed, but it looks like NPM again has the
> wrong
> > version number.
> >
> >
>
>
>


Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-19 Thread Alex Harui
In the past discussion, I suggested a change to the release script that 
apparently never happened and I did not check to see that it happened.  I have 
made the suggested change and we'll see if that change helps on the next 
release.

I think someone could also publish the bits as 0.9.4 if they have time.  I 
don't want to take the time to do that.  I will bump the dev branches to 0.9.6 
this week sometime.  Our next release will have to be 0.9.6, just like we 
skipped 0.9.3.

-Alex

On 11/19/18, 7:25 AM, "OmPrakash Muppirala"  wrote:

Yeah, there is no way to unpublish it.
I'm guessing that the the version number get bumped twice?

On Mon, Nov 19, 2018 at 2:18 AM Harbs  wrote:

> Ouch. Am I correct in assuming that there’s no way to “unpublish” 0.9.5?
>
> Why did this happen again?
>
> Harbs
>
> > On Nov 19, 2018, at 2:54 AM, Alex Harui 
> wrote:
> >
> > Artifacts have been pushed, but it looks like NPM again has the wrong
> version number.
>
>




Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-19 Thread OmPrakash Muppirala
Yeah, there is no way to unpublish it.
I'm guessing that the the version number get bumped twice?

On Mon, Nov 19, 2018 at 2:18 AM Harbs  wrote:

> Ouch. Am I correct in assuming that there’s no way to “unpublish” 0.9.5?
>
> Why did this happen again?
>
> Harbs
>
> > On Nov 19, 2018, at 2:54 AM, Alex Harui 
> wrote:
> >
> > Artifacts have been pushed, but it looks like NPM again has the wrong
> version number.
>
>


NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

2018-11-19 Thread Harbs
Ouch. Am I correct in assuming that there’s no way to “unpublish” 0.9.5?

Why did this happen again?

Harbs

> On Nov 19, 2018, at 2:54 AM, Alex Harui  wrote:
> 
> Artifacts have been pushed, but it looks like NPM again has the wrong version 
> number.



[RESULT][VOTE] Release Apache Royale 0.9.4 RC2

2018-11-19 Thread Alex Harui
Forgot to change subject.

On 11/19/18, 12:00 AM, "Alex Harui"  wrote:

Vote passed.

Artifacts have been pushed, but it looks like NPM again has the wrong 
version number.

-Alex

On 11/14/18, 10:46 AM, "Alex Harui"  wrote:

Hi, 

This is vote for the 0.9.4 release of Apache Royale. 

The release candidate can be found here; 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2F&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=rEjjVXYnRmmQqMQ4dO8OghvkezVUGKk%2B2goJSDbRjLk%3D&reserved=0
 

Before voting please review the section,'What are the ASF requirements 
on 
approving a release?', at: 

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-release&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=ZaqI%2BBWmkzpWIEKUL5jJJwyk%2FJRIxzFwqun26JujS%2BU%3D&reserved=0
 

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 cross-compile a simple example using the 
SDK. 

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 
-royale package and use Apache Ant to run the InstallAdobeSDKs script 
via: 
  ant -f InstallAdobeSDKs.xml 

You may also get the binary packages via NPM.  The -js package can be 
installed via: 

npm install

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-roya&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=TV4GdmHvC0jQGWCnaO3ywb304roQ89yMcazgLNHs0Vc%3D&reserved=0
le-0.9.4-bin-js.tar.gz -g 

The full package with SWF support can be installed via: 

npm install

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=o%2FGD9eghAs22UKDbEPD7OyS9aqsE%2FndubZtALZN%2B2kE%3D&reserved=0{rc}/binaries/apache-r
oyale-0.9.4-bin-js-swf.tar.gz -g

Maven artifacts are staged here: 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1025&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=59Hj17ahave9zJfjapOBE8cG6%2F8dX%2BQrqPNi4CywV3I%3D&reserved=0
 

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 I 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2FApproveRoyale.xml&data=02%7C01%7Caharui%40adobe.com%7C894efec678284e40dfda08d64df519a6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782112424993024&sdata=2cWJOFNu

Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-19 Thread Alex Harui
Vote passed.

Artifacts have been pushed, but it looks like NPM again has the wrong version 
number.

-Alex

On 11/14/18, 10:46 AM, "Alex Harui"  wrote:

Hi, 

This is vote for the 0.9.4 release of Apache Royale. 

The release candidate can be found here; 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2F&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875922919&sdata=QEJPD0rVFzaXgJ6s71k00eanixC3lYl209SyPwKKuVU%3D&reserved=0
 

Before voting please review the section,'What are the ASF requirements on 
approving a release?', at: 

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-release&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=HKBhzhwTqPK%2Bnr0K6f6xZ2aFWTt1woJGknvVUh5DiRI%3D&reserved=0
 

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 cross-compile a simple example using the SDK. 

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 
-royale package and use Apache Ant to run the InstallAdobeSDKs script via: 
  ant -f InstallAdobeSDKs.xml 

You may also get the binary packages via NPM.  The -js package can be 
installed via: 

npm install

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-roya&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=nNZ1G6OXn6NADfuphv9eFwFCzND8gP%2B9ndaXNVJAthU%3D&reserved=0
le-0.9.4-bin-js.tar.gz -g 

The full package with SWF support can be installed via: 

npm install

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=u1Q0pVjkFpAi%2BJQ3q9Kp9uF0Y9RUBom1PiDATS3BI6A%3D&reserved=0{rc}/binaries/apache-r
oyale-0.9.4-bin-js-swf.tar.gz -g

Maven artifacts are staged here: 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1025&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=X%2B4UhG7cT5p%2B%2FORwICilhplHV21atZxIqTY0YfOY%2Fx0%3D&reserved=0
 

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 I 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2FApproveRoyale.xml&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=V0XhcX6pXfVVc8o26TJceMTpYTcSw4oVtlSQnJ76Uks%3D&reserved=0
 
3) run the script: 
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.4 -Drc=2 
   If you want to test SWF support during the approval, use: 
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.4 -Drc=2
-Duse-flash=true 

You are not required to use this script, and more testing of the packages 
an

Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-18 Thread Piotr Zarzycki
+0 (Binding)

I couldn't get to work ant build on my sight - It is probably problem on my
PC, but I decided to vote +0. Apart of that:
- Maven build works perfectly fine
- I was able to build PureMVC sources using staged artifacts
- I was able to build and run TranspiledActionScript example using staged
artifacts

Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y

Thanks,
Piotr


pt., 16 lis 2018 o 23:51 Olaf Krueger  napisał(a):

> Sorry for accidentally polluting the vote thread :-(
> Moved the post to the discussion thread [1]
>
> [1]
>
> http://apache-royale-development.20373.n8.nabble.com/DISCUSS-Discuss-Release-Apache-Royale-0-9-4-RC2-tp7390p7488.html
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*


Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-16 Thread Olaf Krueger
Sorry for accidentally polluting the vote thread :-(
Moved the post to the discussion thread [1]

[1] 
http://apache-royale-development.20373.n8.nabble.com/DISCUSS-Discuss-Release-Apache-Royale-0-9-4-RC2-tp7390p7488.html




--
Sent from: http://apache-royale-development.20373.n8.nabble.com/


Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-16 Thread Olaf Krueger
Hi, 
I run the approval script, but it fails immediately [1].
Do I miss something?
(I am using ant 1.10.1)

Thanks,
Olaf

[1]
PS C:\local\apache-royale\vote_0_9_4_RC2> ant -e -f ApproveRoyale.xml
-Drelease.version=0.9.4 -Drc=2
Buildfile: C:\local\apache-royale\vote_0_9_4_RC2\ApproveRoyale.xml

BUILD FAILED
C:\local\apache-royale\vote_0_9_4_RC2\ApproveRoyale.xml:121: The release
version is not set.  Specify -Drelease.version=

Total time: 0 seconds



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/


Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-16 Thread OmPrakash Muppirala
+1 (binding)

Package
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/apache-royale-0.9.4-src.tar.gz

Java 1.8

OS: Mac OS X x86_64 10.13.6

Source kit signatures match: y

Source kit builds: y

README is ok: y

RELEASE_NOTES is ok: y

NOTICE is ok: y

LICENSE is ok: y

No unapproved licenses or archives: y

No unapproved binaries: y

On Fri, Nov 16, 2018 at 12:45 AM Harbs  wrote:

> +1
> Package
> https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/apache-royale-0.9.4-src.tar.gz
> Java 1.8
> OS: Mac OS X x86_64 10.12.6
> Source kit signatures match: y
> Source kit builds: y
> README is ok: y
> RELEASE_NOTES is ok: y
> NOTICE is ok: y
> LICENSE is ok: y
> No unapproved licenses or archives: y
> No unapproved binaries: y
>
> Package
> https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-royale-0.9.4-bin-js-swf.tar.gz
> Binary kit signatures match: y
> NOTICE is ok: y
> LICENSE is ok: y
> No unapproved licenses or archives in binary package: y
> No unapproved binaries in binary package: y
>
> Harbs


Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-16 Thread Harbs
+1
Package 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/apache-royale-0.9.4-src.tar.gz
Java 1.8
OS: Mac OS X x86_64 10.12.6
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y

Package 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-royale-0.9.4-bin-js-swf.tar.gz
Binary kit signatures match: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives in binary package: y
No unapproved binaries in binary package: y

Harbs

Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-15 Thread Dave Fisher
+1 (binding)

Both source packages are essentially identical.
All packages source and binary have proper signatures and checksums.
RAT Check looks good.
LICENSE and NOTICE good.

Ant Build looks successful
Maven Build has issues which are described in the DISCUSS.

Note there are some CC-SA files (about 8) that were formerly allowed. The 
license needs to be fixed in the next RC or Release.

Regards,
Dave

> On Nov 15, 2018, at 7:19 AM, Josh Tynjala  wrote:
> 
> +1 (binding)
> Package 
> https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/apache-royale-0.9.4-src.zip
> Java 1.8
> OS: Windows 10 amd64 10.0
> Source kit signatures match: y
> Source kit builds: y
> README is ok: y
> RELEASE_NOTES is ok: y
> NOTICE is ok: y
> LICENSE is ok: y
> No unapproved licenses or archives: y
> No unapproved binaries: y
> 
> Package 
> https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-royale-0.9.4-bin-js-swf.zip
> Binary kit signatures match: y
> NOTICE is ok: y
> LICENSE is ok: y
> No unapproved licenses or archives in binary package: y
> No unapproved binaries in binary package: y
> 
> - Josh
> 
> On 2018/11/14 18:45:43, "Alex Harui"  wrote: 
>> Hi, 
>> 
>> This is vote for the 0.9.4 release of Apache Royale. 
>> 
>> The release candidate can be found here; 
>> https://dist.apache.org/repos/dist/dev/royale/0.9.4/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 cross-compile a simple example using the SDK. 
>> 
>> 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 
>> -royale package and use Apache Ant to run the InstallAdobeSDKs script via: 
>>  ant -f InstallAdobeSDKs.xml 
>> 
>> You may also get the binary packages via NPM.  The -js package can be 
>> installed via: 
>> 
>> npm install
>> https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-roya
>> le-0.9.4-bin-js.tar.gz -g 
>> 
>> The full package with SWF support can be installed via: 
>> 
>> npm install
>> https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc{rc}/binaries/apache-r
>> oyale-0.9.4-bin-js-swf.tar.gz -g
>> 
>> Maven artifacts are staged here: 
>> https://repository.apache.org/content/repositories/orgapacheroyale-1025 
>> 
>> 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 I 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.4/rc2/ApproveRoyale.xml 
>> 3) run the script: 
>>   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.4 -Drc=2 
>>   If you want to test SWF support during the approval, use: 
>>   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.4 -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, 
>> Alex Harui 
>> 
>> 



Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-15 Thread Josh Tynjala
+1 (binding)
Package 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/apache-royale-0.9.4-src.zip
Java 1.8
OS: Windows 10 amd64 10.0
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y

Package 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-royale-0.9.4-bin-js-swf.zip
Binary kit signatures match: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives in binary package: y
No unapproved binaries in binary package: y

- Josh

On 2018/11/14 18:45:43, "Alex Harui"  wrote: 
> Hi, 
> 
> This is vote for the 0.9.4 release of Apache Royale. 
> 
> The release candidate can be found here; 
> https://dist.apache.org/repos/dist/dev/royale/0.9.4/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 cross-compile a simple example using the SDK. 
> 
> 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 
> -royale package and use Apache Ant to run the InstallAdobeSDKs script via: 
>   ant -f InstallAdobeSDKs.xml 
> 
> You may also get the binary packages via NPM.  The -js package can be 
> installed via: 
> 
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-roya
> le-0.9.4-bin-js.tar.gz -g 
> 
> The full package with SWF support can be installed via: 
> 
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc{rc}/binaries/apache-r
> oyale-0.9.4-bin-js-swf.tar.gz -g
> 
> Maven artifacts are staged here: 
> https://repository.apache.org/content/repositories/orgapacheroyale-1025 
> 
> 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 I 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.4/rc2/ApproveRoyale.xml 
> 3) run the script: 
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.4 -Drc=2 
>If you want to test SWF support during the approval, use: 
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.4 -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, 
> Alex Harui 
> 
> 


Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-14 Thread Alex Harui
Because coming in now with possible issues is disruptive to the community.  If 
you want to help us, you would watch the commits.

The source for this text is Wikipedia, which is not a software provider.

I think we're good for now.  If we do another RC for a real reason, we'll pull 
these files as they aren't critical.

-Alex

On 11/14/18, 6:09 PM, "Justin Mclean"  wrote:

Hi,

Text is not media (media as defined in that thread is images, audio or
video) and it's been modified.

Why would I be closely watching the commits when I'm not a committer or PMC
member?

Probably best to continue this in the discussion thread.

Thanks,
Justin

On Thu., 15 Nov. 2018, 12:55 pm Alex Harui  It isn't code, it is text media.
>
> Thanks for trying though.  Remember, you are supposed to be watching the
> commits, not the vote threads.
>
> -Alex
>
> On 11/14/18, 5:47 PM, "Justin Mclean"  wrote:
>
> Hi,
>
> -1 (non-binding)
>
> The release includes CC-SA licensed content [1] which is not
> unmodified media [2].
>
> I know this content [1] was copied from TourDeFlex in the Flex project
> so it may also have an issue. It looks like policy has changed (or been
> clarified) since the last TourDeFlex release in 2014, for instance see the
> discussion here [3] in 2017. Note the draft email in that discussion
> clarifying inclusion of CC licensed content, but I cannot recall if it was
> sent out to all PMCs.
>
> Thanks,
> Justin
>
> 1. ./royale-asjs/examples/mxroyale/tourdeflexmodules/src/apache/
> 2.
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sa&data=02%7C01%7Caharui%40adobe.com%7C5978c8df10824a4fc8f108d64a9f6fb9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778445992506299&sdata=d9QTyVLz%2BBNDBg0dVV3sDAUQOIHvZVMpbAq5L5o3f1I%3D&reserved=0
> 3.
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F46b628e47e2461834066835ff7d696b2a55e00cf81a98b4daed444f0%40%253Clegal-discuss.apache.org%253E&data=02%7C01%7Caharui%40adobe.com%7C5978c8df10824a4fc8f108d64a9f6fb9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778445992516304&sdata=pE58FF9bA55LYOgQAlqlY1PoFZiMI4l98yXEJCwVoWw%3D&reserved=0
>
>




Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-14 Thread Justin Mclean
Hi,

Text is not media (media as defined in that thread is images, audio or
video) and it's been modified.

Why would I be closely watching the commits when I'm not a committer or PMC
member?

Probably best to continue this in the discussion thread.

Thanks,
Justin

On Thu., 15 Nov. 2018, 12:55 pm Alex Harui  It isn't code, it is text media.
>
> Thanks for trying though.  Remember, you are supposed to be watching the
> commits, not the vote threads.
>
> -Alex
>
> On 11/14/18, 5:47 PM, "Justin Mclean"  wrote:
>
> Hi,
>
> -1 (non-binding)
>
> The release includes CC-SA licensed content [1] which is not
> unmodified media [2].
>
> I know this content [1] was copied from TourDeFlex in the Flex project
> so it may also have an issue. It looks like policy has changed (or been
> clarified) since the last TourDeFlex release in 2014, for instance see the
> discussion here [3] in 2017. Note the draft email in that discussion
> clarifying inclusion of CC licensed content, but I cannot recall if it was
> sent out to all PMCs.
>
> Thanks,
> Justin
>
> 1. ./royale-asjs/examples/mxroyale/tourdeflexmodules/src/apache/
> 2.
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sa&data=02%7C01%7Caharui%40adobe.com%7Cd5290b347b224c81627808d64a9c4924%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778432440457156&sdata=x1RJCKF5WNuL%2FFgr02NPgDtlZ4fGahROEmm3sK29pbc%3D&reserved=0
> 3.
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F46b628e47e2461834066835ff7d696b2a55e00cf81a98b4daed444f0%40%253Clegal-discuss.apache.org%253E&data=02%7C01%7Caharui%40adobe.com%7Cd5290b347b224c81627808d64a9c4924%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778432440457156&sdata=iaewUj%2BZ4%2F3J8mubTYeASR4jAwIjQIVQSeYFJjcGL%2FY%3D&reserved=0
>
>


Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-14 Thread Alex Harui
It isn't code, it is text media.

Thanks for trying though.  Remember, you are supposed to be watching the 
commits, not the vote threads.

-Alex

On 11/14/18, 5:47 PM, "Justin Mclean"  wrote:

Hi,

-1 (non-binding)

The release includes CC-SA licensed content [1] which is not unmodified 
media [2].

I know this content [1] was copied from TourDeFlex in the Flex project so 
it may also have an issue. It looks like policy has changed (or been clarified) 
since the last TourDeFlex release in 2014, for instance see the discussion here 
[3] in 2017. Note the draft email in that discussion clarifying inclusion of CC 
licensed content, but I cannot recall if it was sent out to all PMCs.

Thanks,
Justin

1. ./royale-asjs/examples/mxroyale/tourdeflexmodules/src/apache/
2. 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sa&data=02%7C01%7Caharui%40adobe.com%7Cd5290b347b224c81627808d64a9c4924%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778432440457156&sdata=x1RJCKF5WNuL%2FFgr02NPgDtlZ4fGahROEmm3sK29pbc%3D&reserved=0
3. 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F46b628e47e2461834066835ff7d696b2a55e00cf81a98b4daed444f0%40%253Clegal-discuss.apache.org%253E&data=02%7C01%7Caharui%40adobe.com%7Cd5290b347b224c81627808d64a9c4924%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778432440457156&sdata=iaewUj%2BZ4%2F3J8mubTYeASR4jAwIjQIVQSeYFJjcGL%2FY%3D&reserved=0



Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-14 Thread Justin Mclean
Hi,

-1 (non-binding)

The release includes CC-SA licensed content [1] which is not unmodified media 
[2].

I know this content [1] was copied from TourDeFlex in the Flex project so it 
may also have an issue. It looks like policy has changed (or been clarified) 
since the last TourDeFlex release in 2014, for instance see the discussion here 
[3] in 2017. Note the draft email in that discussion clarifying inclusion of CC 
licensed content, but I cannot recall if it was sent out to all PMCs.

Thanks,
Justin

1. ./royale-asjs/examples/mxroyale/tourdeflexmodules/src/apache/
2. https://www.apache.org/legal/resolved.html#cc-sa
3. 
https://lists.apache.org/thread.html/46b628e47e2461834066835ff7d696b2a55e00cf81a98b4daed444f0@%3Clegal-discuss.apache.org%3E

Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-14 Thread Alex Harui
+1
Package 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/apache-royale-0.9.4-src.tar.gz
Java 1.8
OS: Mac OS X x86_64 10.12.6
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y

Package 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-royale-0.9.4-bin-js-swf.tar.gz
Binary kit signatures match: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives in binary package: y
No unapproved binaries in binary package: y

On 11/14/18, 10:46 AM, "Alex Harui"  wrote:

Hi, 

This is vote for the 0.9.4 release of Apache Royale. 

The release candidate can be found here; 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2F&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875922919&sdata=QEJPD0rVFzaXgJ6s71k00eanixC3lYl209SyPwKKuVU%3D&reserved=0
 

Before voting please review the section,'What are the ASF requirements on 
approving a release?', at: 

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-release&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=HKBhzhwTqPK%2Bnr0K6f6xZ2aFWTt1woJGknvVUh5DiRI%3D&reserved=0
 

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 cross-compile a simple example using the SDK. 

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 
-royale package and use Apache Ant to run the InstallAdobeSDKs script via: 
  ant -f InstallAdobeSDKs.xml 

You may also get the binary packages via NPM.  The -js package can be 
installed via: 

npm install

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-roya&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=nNZ1G6OXn6NADfuphv9eFwFCzND8gP%2B9ndaXNVJAthU%3D&reserved=0
le-0.9.4-bin-js.tar.gz -g 

The full package with SWF support can be installed via: 

npm install

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=u1Q0pVjkFpAi%2BJQ3q9Kp9uF0Y9RUBom1PiDATS3BI6A%3D&reserved=0{rc}/binaries/apache-r
oyale-0.9.4-bin-js-swf.tar.gz -g

Maven artifacts are staged here: 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1025&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=X%2B4UhG7cT5p%2B%2FORwICilhplHV21atZxIqTY0YfOY%2Fx0%3D&reserved=0
 

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 I 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2FApproveRoyale.xml&data=02%7C01%7Caharui%40adobe.com%7Ccd9e8

[VOTE] Release Apache Royale 0.9.4 RC2

2018-11-14 Thread Alex Harui
Hi, 

This is vote for the 0.9.4 release of Apache Royale. 

The release candidate can be found here; 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/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 cross-compile a simple example using the SDK. 

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 
-royale package and use Apache Ant to run the InstallAdobeSDKs script via: 
  ant -f InstallAdobeSDKs.xml 

You may also get the binary packages via NPM.  The -js package can be 
installed via: 

npm install
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-roya
le-0.9.4-bin-js.tar.gz -g 

The full package with SWF support can be installed via: 

npm install
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc{rc}/binaries/apache-r
oyale-0.9.4-bin-js-swf.tar.gz -g

Maven artifacts are staged here: 
https://repository.apache.org/content/repositories/orgapacheroyale-1025 

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 I 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.4/rc2/ApproveRoyale.xml 
3) run the script: 
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.4 -Drc=2 
   If you want to test SWF support during the approval, use: 
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.4 -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, 
Alex Harui