Side note...I searched for javadoc or maven-javadoc-pluign and didn't find
anything
So it's a completely mystery to me how release process is triggering the
creation of javadocs. :?
El dom., 30 sept. 2018 a las 17:47, Carlos Rovira ()
escribió:
> Hi Om,
>
> error is now fixed. Can you try to
Hi,
just reverted the two generated commits for release, I left to you remove
new branches generated.
About the fail, I was wrong, since I saw this very quickly. It's not about
JDK, I'm using as well 1.8. I was confused for other thing I had some weeks
ago, and was trying to use another JDK, but
Hi, since I'm going to work now on some compiler changes, I'll revert those
2 commits in each repo. I'll try to pass as well maven with java 1.8 in amp
and see if I get the same error
El dom., 30 sept. 2018 a las 15:16, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Om,
>
> I think if
Om,
I think if you got fail during the process you should right after that.
1) Remove created release tags
2) Revert all changes which Maven did in develop branches to the previous
state
Thanks,
Piotr
niedz., 30 wrz 2018 o 12:40 Carlos Rovira
napisał(a):
> Hi Om,
> don't have many time now,
Hi Om,
don't have many time now, but seems you are using JDK 1.8 and that project
needs to be 1.7 or will fail
I'll connect some hours later to see if you could use that sdk
good luck! :)
El dom., 30 sept. 2018 a las 11:34, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Hi Om,
>
>
Hi Om,
Have you tried build that example on their own? Is it failing with the same
stack trace?
Thanks,
Piotr
On Sun, Sep 30, 2018, 9:31 AM OmPrakash Muppirala
wrote:
> So, I made a lot of progress (much more than last time), but unfortunately
> the build failed at this stage. Looks like an
So, I made a lot of progress (much more than last time), but unfortunately
the build failed at this stage. Looks like an issue with the
SampleAmfWebApp. Anyone else seeing this error or am I doing something
wrong?
[exec] [INFO] [INFO] Apache Royale: Examples: Native: USStatesMap
...
Okay, trying now.
On Tue, Sep 25, 2018 at 9:52 AM Piotr Zarzycki
wrote:
> Om,
>
> I think if you first try to build Royale framework with Maven all the
> dependencies will be downloaded. During framework build you should get
> question about license related to player global etc. Once you do
t;> > > -Alex
> > > >> > >
> > > >> > >
> > > >> > > On 9/14/18, 8:05 AM, "Piotr Zarzycki" <
> > >
> inside pluginManagement tag what version
> of scm
> > is
> > >> used - It will
> > >> > > download
> > >> > > some older one.
> >
t; > happen. I've figure out that if Maven is
> using
> > scm
> > >> and we won't
> > >> > specify
> > >> > > inside pluginManageme
Om,
I think if you first try to build Royale framework with Maven all the
dependencies will be downloaded. During framework build you should get
question about license related to player global etc. Once you do successful
build you could try to go and play with script for release. - That way to
According to the archives, try running:
mvn -s settings-template.xml clean install
Thanks,
-Alex
On 9/23/18, 3:48 PM, "OmPrakash Muppirala" wrote:
On Sun, Sep 23, 2018 at 3:43 PM OmPrakash Muppirala
wrote:
> Thanks. I decided to stick with 1.8 :-)
>
>
BTW,
Thanks. I decided to stick with 1.8 :-)
I am seeing this error:
[ERROR] Failed to execute goal
org.apache.royale.compiler:royale-maven-plugin:0.9.4-SNAPSHOT:compile-as
(default-compile-as) on project Core: Could not resolve dependencies for
project
Hi Om,
I have Java 8 and 10 installed, and I think I was able to compile three
repos, but I find AMF java example doesn't work, since BlazeDS needs a
Lower version I need to go with 8 for this example. Maybe other part needs
as well 7 or 8.
I think trying another SDK should be left to some time
Okay trying this out now.
First question: The release doc [1] says we need Java 1.7 or higher. Has
anyone tried Java 10? That is the default version available through all
installation channels.
Any pitfalls I should consider?
Thanks,
Om
On Fri, Sep 21, 2018 at 12:23 PM Carlos Rovira
wrote:
I think we are ready to go, so let's go! ;-)
Good luck Om! :)
El vie., 21 sept. 2018 a las 18:19, Alex Harui ()
escribió:
> Yes, I think they are ready. I removed the release/0.9.4 branches so the
> scripts should be able to make a new one.
>
> -Alex
>
> On 9/21/18, 8:58 AM, "OmPrakash
Yes, I think they are ready. I removed the release/0.9.4 branches so the
scripts should be able to make a new one.
-Alex
On 9/21/18, 8:58 AM, "OmPrakash Muppirala" wrote:
Alex said in his last email that the repos are ready. Will try in a few
minutes.
Thanks,
Om
Alex said in his last email that the repos are ready. Will try in a few
minutes.
Thanks,
Om
On Fri, Sep 21, 2018, 7:24 AM Piotr Zarzycki
wrote:
> Om,
>
> In my opinion you have everything ready to go! Since develop is ready
> probably you will start doing steps from the beginning, so in the
Om,
In my opinion you have everything ready to go! Since develop is ready
probably you will start doing steps from the beginning, so in the results
we will get branches release/0.9.4. However they already exists, because of
my previous attempt.
Maybe before you even start they need to be
So am I clear to try and release? Or should I wait for any other feature
or bug?
Thanks,
Om
On Fri, Sep 21, 2018, 6:20 AM Carlos Rovira wrote:
> Hi Alex
>
> El vie., 21 sept. 2018 a las 3:06, Alex Harui ()
> escribió:
>
> > I made some adjustments to the repos so that they "should" be ready
Hi Alex
El vie., 21 sept. 2018 a las 3:06, Alex Harui ()
escribió:
> I made some adjustments to the repos so that they "should" be ready to run
> the scripts and produce the 0.9.4 release. Of course, I could be wrong.
> We'll see how Om fares.
>
>
so cool :)
> I also put in a change that
Hey Om,
If you have capacity please finish that release. Users of VSCode and
Moonshine will be happy!
Thanks,
Piotr
On Thu, Sep 20, 2018, 5:08 PM OmPrakash Muppirala
wrote:
> The last time I tried to release, it was on Windows PC. Some tweaks were
> required. Also, I would say that the
I made some adjustments to the repos so that they "should" be ready to run the
scripts and produce the 0.9.4 release. Of course, I could be wrong. We'll see
how Om fares.
I also put in a change that should fix the dependencies issue. So the
remaining questions are around the AMF problem.
Hi Om,
that's great! :)
Hope you could take on the release and get it out of the door :)
Thanks!
Carlos
El jue., 20 sept. 2018 a las 17:08, OmPrakash Muppirala (<
bigosma...@gmail.com>) escribió:
> The last time I tried to release, it was on Windows PC. Some tweaks were
> required. Also,
The last time I tried to release, it was on Windows PC. Some tweaks were
required. Also, I would say that the release process was too automated
As a result I was not able to figure out what exaxtly broke, etc.
FWIW, I have a Mac now. I can try again if Piotr wants to take a break.
Getting
Hi Alex,
thanks you see it in the list of unread messages and will go to say that I
found it.
I'll take a look now
El jue., 20 sept. 2018 a las 9:44, Alex Harui ()
escribió:
>
>
> On 9/19/18, 11:49 PM, "Carlos Rovira" wrote:
>
> Hi Alex,
>
> what Zend-AMF issue you refer? can you
On 9/19/18, 11:49 PM, "Carlos Rovira" wrote:
Hi Alex,
what Zend-AMF issue you refer? can you post the link to that issue?
thanks
https://lists.apache.org/list.html?us...@royale.apache.org
PD: about your preoccupation, we'll have issues for many months to come. I
Hi Alex,
what Zend-AMF issue you refer? can you post the link to that issue?
thanks
PD: about your preoccupation, we'll have issues for many months to come. I
see each day in Jewel as I go here and there fixing or completing issues I
find, so I think is ok release with that issues so people can
Jewel is another reason.
Carlos wrote a lot of blog posts which can’t be run until we release.
(Plus lots of little things that were fixed…)
> On Sep 19, 2018, at 11:26 PM, Piotr Zarzycki
> wrote:
>
> I personally express important reason. Releasing can help community around
> VSCode and
I personally express important reason. Releasing can help community around
VSCode and Moonshine.
Piotr
On Wed, Sep 19, 2018, 9:41 PM Alex Harui wrote:
> What do you see as the important reasons? I know the Apache mantra is to
> release early and often, but if it were up to me, we would
What do you see as the important reasons? I know the Apache mantra is to
release early and often, but if it were up to me, we would release after we hit
some interesting milestone, like getting Alina's app to compile completely, or
someone else says they are ready to go to production and need
I’m happy to try and be a release manager, but I don’t have time for at least a
month. I think it’s pretty important to get this release out sooner rather than
later.
If you can help Piotr finish this release, I’ll try to do the 0.9.5 release.
Thanks,
Harbs
> On Sep 19, 2018, at 6:54 PM, Alex
Process is definitely automated. If we would not skip version we would have
RC1 two days ago from me. I got dedicated time for making that release,
cause it can help improve Josh's plugin - which is using Royale compiler.
As you know that plugin is used in VSCode and Moonshine, so Framework part
IMO, speculating things to be worse than they are without being informed is not
good for the community.
Piotr ran into problems because we were forced to try to skip a version.
Again, there is nobody whose job it is to make releasing simple, and who will
take the time to try to anticipate
Hi Alex,
don't think each comment is negative only because is not positive! I
already said some words recognizing the huge effort behind that task. I
know how hard it is.
But as I said the great work done, I want to expose the only point I think
is problematic, the difficult of the process. And I
Hi Piotr,
sorry to hear that, I think we're out of resources. I'm concentrating in
make Jewel as stable as possible since in few days we can start a new
project with Royale-Jewel, so I still don't know how I'll be doing to
continuer Jewel, make that project and continue with my other tasks that
Btw. The process is quite automatic, but skipping the version wasn't
something considered before.
On Wed, Sep 19, 2018, 1:31 PM Piotr Zarzycki
wrote:
> Carlos,
>
> Unfortunately I'm giving up doing that. I have spent on this too much time
> and money. Someone else can continue from my point.
>
Carlos,
Unfortunately I'm giving up doing that. I have spent on this too much time
and money. Someone else can continue from my point.
Dev branch is setup to 0.9.4-SNAPSHOT. Even with detailed instruction from
Alex I don't know what to do next.
Details are in previous email.
Good Luck!
Piotr
Hi Piotr,
I encourage you and Alex to try to refine more the process so we can
release more easily. I think right now the process is very dependent of
many manual tasks, and that impact in all: huge effort to do the release,
many time involved, impossible to reproduce in next release,..
I think
We are releasing from specific commit. The problem is laying out on setup
appropriate values for ANT build and Maven build. This is where all
failing.
All the problem is happening because we need omit one version, cause npm
was updated with 0.9.3 - Not sure why.
Update of version should happen
Hi Olaf,
hehe, I think we overlap and mostly said the same ;-)
for me that's the right way.
Thanks
El mié., 19 sept. 2018 a las 10:57, Olaf Krueger ()
escribió:
> > I think there should be some rules where during release process
> committing
> > to develop is stopped.
>
> What do you think
> > picking up.
> > > >> > >
> > > >> > > HTH,
> > > >> > > -Alex
> &g
> I think there should be some rules where during release process committing
> to develop is stopped.
What do you think about creating a "release/v0.9.x" branch which has to be
merged back to master and dev after the release is done instead of doing the
release from dev?
Thanks for doing all
; weird
> > >> > > happen. I've figure out that if Maven is
> using
> > scm
> > >> and we won't
> > >> > specify
> > >> > > inside pluginManageme
gt; > > 1) If I run build of royale-compiler using cmd
> or
> >> even from
> >> > Intellij -
> >> > > scm
> >> > > 1.10.0 i
>> > > and Maven.
> >> > >
> >> > > 1) If I run build of royale-compiler using cmd
> or
> >> even from
> >> > Intellij -
> >> > > scm
> >> >
> > Unfortunately I don't know how to check that. I can
>> check only
>> > > "Effective
>> > > > Pom" - Intellij is able to show me what is behind
>> the stage in
>> > > specific
>
01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FBzVxdata=02%7C01%7Caharui%40adobe.com%7C934bc998d2aa4047650608d61a5ea3ec%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636725391117848678sdata=HkqvuTmMuZFzFZhOEDFmpG94uJ3My3G7rCI8P0UQgFQ%3Dreserved=0
> >
> being
>> > > downloaded 1.9.4
>> > >
>> > > Any idea why it could happen like that ? This file
>> > > releasecandidate.xml is
>> > > used t
t; > downloaded. You can also check out the local maven cache.
> > >
> > > Get Outlook for Android<
> >
>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Caharui%40adobe.com%7C934bc998d2aa4047650608d61a5ea3ec%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636725391117848678sdata
; > > downloaded. You can also check out the local maven cache.
> > >
> > > Get Outlook for Android<
> >
>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Caharui%40adobe.com%7Ce7d71e7fef09469b292908d61a5d0675%7Cfa7b1b5a7b3443
are
> > > downloaded. You can also check out the local maven cache.
> > >
> > > Get Outlook for Android<
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Caharui%40adobe.com%7C52945277f0d64479c60c08d61a5b879b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6367253
?
> > >
> > > Get Outlook for Android<
> >
>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Caharui%40adobe.com%7C52945277f0d64479c60c08d61a5b879b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63672533552343sdata=SVi8NTxA06PTjMvNX9q9x
dobe.com%7C85b74180eeec4cdfe9c108d61a5392e1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636725343577797160sdata=bvG%2B%2FoQcFS5GlG9yv7qen9vN5SgH5dlPqDCORMCRw0s%3Dreserved=0
> >
> >
> > ________
> > From: Piotr Zarzycki
> > Sent
> From: Piotr Zarzycki
> Sent: Thursday, September 13, 2018 11:02:29 AM
> To: dev@royale.apache.org
> Subject: Re: [Discuss] Start release process 0.9.3
>
> Unfortunately I don't know how to check that. I can check only "Effective
> Pom" -
ndroid<https://aka.ms/ghei36>
>
>
> From: Piotr Zarzycki
> Sent: Thursday, September 13, 2018 11:02:29 AM
> To: dev@royale.apache.org
> Subject: Re: [Discuss] Start release process 0.9.3
>
> Unfortunately I don't know how to che
o: dev@royale.apache.org
Subject: Re: [Discuss] Start release process 0.9.3
Unfortunately I don't know how to check that. I can check only "Effective
Pom" - Intellij is able to show me what is behind the stage in specific
pom. This is how it looks like for main pom in royale-asjs
arui napisał(a):
> Is maven using scm 1.10?
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
>
> From: Piotr Zarzycki
> Sent: Thursday, September 13, 2018 8:55:29 AM
> To: dev@royale.apache.org
> Subject: Re: [Discuss] Sta
ection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Caharui%40adobe.com%7C66ebbe838a334996dad408d6194dea8b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636724219773081310sdata=3qd%2BPG2I%2Fx3EI%2B6l%2FvaQ7WonR%2B8%2FCs%2FBHGiNJxf6e%2FQ%3Dreserved=0
> > >
> >
> > _
> >
>
>
> From: Piotr Zarzycki
> Sent: Wednesday, September 12, 2018 9:54:04 AM
> To: dev@royale.apache.org
> Subject: Re: [Discuss] Start release process 0.9.3
>
> That's not good, bec
9199530431sdata=au%2Bv6Q11XELrbgSPakwSNbkRto%2Bro09H6X5mrvD2Y6I%3Dreserved=0
> >
>
>
> From: Piotr Zarzycki
> Sent: Wednesday, September 12, 2018 9:54:04 AM
> To: dev@royale.apache.org
> Subject: Re: [Discuss] Start release process 0.9.3
>
>
%3Dreserved=0>
From: Piotr Zarzycki
Sent: Wednesday, September 12, 2018 9:54:04 AM
To: dev@royale.apache.org
Subject: Re: [Discuss] Start release process 0.9.3
That's not good, because I was updated that stuff. It looks like it didn't
work well. Let me investigate
rotection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Caharui%40adobe.com%7Cce0051229b914694495908d618d06964%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636723680739729425sdata=SKlzSys0RQJ0Ei%2F6GUK6sYS%2F1%2BYI4n9ZhplBO8tNRbk%3Dreserved=0
> >
> >>&g
k.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Caharui%40adobe.com%7Cf90551c21c3444754a8508d618c6ecc6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636723639988047590sdata=QI8kHilW7ewe1YOtklgxogJu%2F6oYYk2WHw4X2FBQSb8%3Dreserved=0
> >
> >>>>
> >>>> __
think the only thing I have in the folder is
>>>> releasecandidate.xml and local.properties.
>>>>
>>>> Get Outlook for Android<https://aka.ms/ghei36>
>>>>
>>>>
>>>> From: Piotr
lder is
>>> releasecandidate.xml and local.properties.
>>>
>>> Get Outlook for Android<https://aka.ms/ghei36>
>>>
>>>
>>> From: Piotr Zarzycki
>>> Sent: Wednesday, September 12, 2018 7:42:06 A
Btw. Should I run that command: ant -f releasecandidate.xml
-Drelease.version=x.y.z -Drc=1 make_branches from CMD or Powershell - Does
it make any difference ? It doesn't look like but I prefer to make sure.
I'm using right now CMD.
Thanks,
Piotr
śr., 12 wrz 2018 o 16:47 Piotr Zarzycki
Alex,
It looks to you like SSH problem related?
On Wed, Sep 12, 2018, 4:43 PM Piotr Zarzycki
wrote:
> I think I didn't miss any single point.
>
> On Wed, Sep 12, 2018, 4:42 PM Piotr Zarzycki
> wrote:
>
>> Yes I follow the SSH link. I will review stuff again.
>>
>>
>> On Wed, Sep 12, 2018,
I think I didn't miss any single point.
On Wed, Sep 12, 2018, 4:42 PM Piotr Zarzycki
wrote:
> Yes I follow the SSH link. I will review stuff again.
>
>
> On Wed, Sep 12, 2018, 4:06 PM Alex Harui wrote:
>
>> Did you follow the SSH link from here?
>>
Yes I follow the SSH link. I will review stuff again.
On Wed, Sep 12, 2018, 4:06 PM Alex Harui wrote:
> Did you follow the SSH link from here?
> https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
>
> HTH,
> -Alex
>
> On 9/12/18, 4:55 AM, "Piotr Zarzycki" wrote:
>
> I got
Did you follow the SSH link from here?
https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
HTH,
-Alex
On 9/12/18, 4:55 AM, "Piotr Zarzycki" wrote:
I got first fail using releasecandidate.xml script [1]. It is fail during
git push, so I thought that I will try to run that
I got first fail using releasecandidate.xml script [1]. It is fail during
git push, so I thought that I will try to run that command which seems to
be cause of the problem
git push g...@github.com:apache/royale-compiler.git
refs/heads/develop:refs/heads/develop
but with fetch
git fetch
Hi Harbs,
What's your progress on fixing that or eventually moving to branch ? Can I
proceed with stuff ?
Thanks,
Piotr
śr., 12 wrz 2018 o 07:33 Alex Harui napisał(a):
> Speaking of upgrading, I think you will need to use the latest maven or
> somehow get Maven to use version 1.10.0 of the
Speaking of upgrading, I think you will need to use the latest maven or somehow
get Maven to use version 1.10.0 of the Maven SCM Plugin.
I have most recently tweaked the Ant scripts to generate the required file
extension on the SHA hashes. Assuming those changes work, we should be good to
In case of upgrading anything I really suggest to leave it for the next
release. If you upgrade something you have to take care of upgrading
maven's pom as well.
Piotr
On Tue, Sep 11, 2018, 8:54 PM Alex Harui wrote:
> I am still trying to fix the Maven build of the examples. Harb's change
>
I am still trying to fix the Maven build of the examples. Harb's change seems
satisfactory for at least now.
-Alex
On 9/11/18, 11:47 AM, "Harbs" wrote:
It should be good to go now unless Alex or someone else has objections…
> On Sep 11, 2018, at 8:55 PM, Piotr Zarzycki
wrote:
It should be good to go now unless Alex or someone else has objections…
> On Sep 11, 2018, at 8:55 PM, Piotr Zarzycki wrote:
>
> No problem. Thank you! If I start anything with release that would be
> tomorrow morning or evening my time.
>
> Piotr
>
> wt., 11 wrz 2018 o 19:54 Harbs
I was about to do this, but I don’t know where to find the checksum for the new
file…
If it’s not important, I’ll find other things to do… ;-)
> On Sep 11, 2018, at 9:29 PM, Alex Harui wrote:
>
> If you have time, feel free. I think royale-compiler is just grabbing some
> simple externs for
If you have time, feel free. I think royale-compiler is just grabbing some
simple externs for some simple tests, so not sure how much it matters.
-Alex
On 9/11/18, 11:27 AM, "Harbs" wrote:
Interestingly, it looks like royale-compiler is downloading v20170626, but
royale-asjs is
Interestingly, it looks like royale-compiler is downloading v20170626, but
royale-asjs is downloading v20170910…
Should we fix this?
> On Sep 11, 2018, at 8:50 PM, Piotr Zarzycki wrote:
>
> I think we are using following version from 20170626.
I figured out a solution which should make Alex happy. (i.e. with correct
annotations) I’ll be committing shortly.
> On Sep 11, 2018, at 8:55 PM, Piotr Zarzycki wrote:
>
> No problem. Thank you! If I start anything with release that would be
> tomorrow morning or evening my time.
>
> Piotr
>
+1 for releasing sooner than later :-)
I plan to make some time to test things out.
Thanks,
Om
On Tue, Sep 11, 2018 at 10:55 AM Piotr Zarzycki
wrote:
> No problem. Thank you! If I start anything with release that would be
> tomorrow morning or evening my time.
>
> Piotr
>
> wt., 11 wrz 2018 o
No problem. Thank you! If I start anything with release that would be
tomorrow morning or evening my time.
Piotr
wt., 11 wrz 2018 o 19:54 Harbs napisał(a):
> I’m going to spend a few minutes now to see if I can resolve this simply.
> If not, I’ll revert.
>
> Harbs
>
> > On Sep 11, 2018, at
I’m going to spend a few minutes now to see if I can resolve this simply. If
not, I’ll revert.
Harbs
> On Sep 11, 2018, at 8:50 PM, Piotr Zarzycki wrote:
>
> Hi Harbs,
>
> It would be great if you could do that. You could bring back changes again
> after release and discuss whatever needed.
Hi Harbs,
It would be great if you could do that. You could bring back changes again
after release and discuss whatever needed.
I think we are using following version from 20170626.
Thanks,
Piotr
wt., 11 wrz 2018 o 19:39 Harbs napisał(a):
> I can revert the changes if that’s what folks want.
I can revert the changes if that’s what folks want. We’re going to have trace
calls output if I do that, but we can resolve that for the next release.
I’m going to see if a different version of the closure compiler plays better.
The latest version throws a NoSuchMethod error on
I think is better move that changes to a branch and release.
thanks
El lun., 10 sept. 2018 a las 20:59, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Harbs,
>
> Can you comment on that ? Any chance to move that changes to branch ?
>
> Thanks,
> Piotr
>
> pon., 10 wrz 2018 o 20:54
Yes. I think we are using the wrong annotation for variable number of
parameters.
-Alex
On 9/10/18, 11:49 AM, "Piotr Zarzycki" wrote:
Alex,
What trace hack are you referring to ? This is related what Harbs commits ?
Thanks,
Piotr
pon., 10 wrz 2018 o 20:47
Alex,
What trace hack are you referring to ? This is related what Harbs commits ?
Thanks,
Piotr
pon., 10 wrz 2018 o 20:47 Alex Harui napisał(a):
> FWIW, I am not in favor of releasing with the current trace hack in the
> compiler. But if other's are ok with it, I'm not going to make a big
FWIW, I am not in favor of releasing with the current trace hack in the
compiler. But if other's are ok with it, I'm not going to make a big deal out
of it, I'll just abstain from voting.
-Alex
On 9/10/18, 1:15 AM, "Piotr Zarzycki" wrote:
Hi,
I have prepared today all stuff
Hi,
I have prepared today all stuff which is needed for making RC branch. I
will check whether everything is working tomorrow. In the other words
probably tomorrow I will push RC1 branch.
Thanks,
Piotr
sob., 8 wrz 2018 o 18:55 Piotr Zarzycki
napisał(a):
> Hi Guys,
>
> I see that typedefs
Hi Piotr,
I'll try tomorrow to fix maven distribution, but if I get it or not, you
can go on Monday and start release process.
I have many things on the plate, but all of that will have to wait for next
release after this ;)
Thanks!
El sáb., 8 sept. 2018 a las 18:55, Piotr Zarzycki (<
Hi Guys,
I see that typedefs build is up and running. Is there anything important
which you would like to add?
I wanted to start on Monday playing with release.
Thanks,
Piotr
On Thu, Sep 6, 2018, 6:05 PM Piotr Zarzycki
wrote:
> Hi Alex,
>
> Is there anything I need to know before I jump into
Hi,
I was thinking that we have debug broken right? I mean, we started a thread
about debug (in browsers or in IDEs) and I think nobody here could debug at
that time.
Was someone successful at that time? if this is broken, I think it would be
good to take a look at this issue since this could be
I have pushed changes to feature/MXRoyale that get the MX examples in TDF that
use components that Alina is using to compile. The feature/MXRoyale branch
passed its tests. I merged that to develop and the tests are failing. So I
will be looking into that now.
Then I will look at Maven
Ok so I will wait for your changes.
On Thu, Sep 6, 2018, 6:34 PM Alex Harui wrote:
> It has been so long since I did a release that I don't know of any mental
> notes that I didn't write down.
>
> First we have to fix Maven builds. I will be spending my time on getting
> my last set of changes
Hi Alex,
Is there anything I need to know before I jump into your notes [1] and
start play with develop for release ?
[1] https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
Thanks,
Piotr
czw., 6 wrz 2018 o 09:08 Piotr Zarzycki
napisał(a):
> Hi Guys,
>
> I was trying to check
Awesome! :-)
> On Sep 6, 2018, at 4:26 PM, Piotr Zarzycki wrote:
>
> I will get my hands dirty with release process tomorrow.
>
> czw., 6 wrz 2018 o 15:24 Harbs napisał(a):
>
>> OK. Done.
>>
>>> On Sep 6, 2018, at 4:20 PM, Piotr Zarzycki
>> wrote:
>>>
>>> I'm ok with merging back to
I will get my hands dirty with release process tomorrow.
czw., 6 wrz 2018 o 15:24 Harbs napisał(a):
> OK. Done.
>
> > On Sep 6, 2018, at 4:20 PM, Piotr Zarzycki
> wrote:
> >
> > I'm ok with merging back to develop, since everything seems to be
> working.
>
>
--
Piotr Zarzycki
Patreon:
101 - 200 of 355 matches
Mail list logo
