A brief message from your friendly Release Manager:
I don't consider the issues Justin uncovered after belatedly testing
the RC to be blockers. Please continue voting, there's still a day
left before I start counting ;-)
EdB
On Wed, Jan 21, 2015 at 8:51 AM, Alex Harui wrote:
>
>
> On 1/20/15,
Hi,
> I don't consider the issues Justin uncovered after belatedly testing
> the RC to be blockers. Please continue voting, there's still a day
> left before I start counting ;-)
IMO License issues, the locale issue and RSL issue (a regression) are all
blockers, unless we fix these and make anot
Hi,
> I don’t think I’m seeing this. If the first thing I do in the UI is
> choose a new locale, when I get to the license list, it looks right to me.
Reproducible every time for me. Are you sure you're running 3.1?
> AFAIK, it’s been this way for quite some time now.
But not in the current
Hi,
We also missing the recently added fonts etc if you want to add those while
you're in there.
Thanks,
Justin
I agree with Justin. Once you build your application and it is simply doesn't
work because of the SDK issue it is a blocker.
I haven't vote yet just because I didn't check any existing application with
current SDK.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in
On 1/21/15, 12:37 AM, "Justin Mclean" wrote:
>Hi,
>
>We also missing the recently added fonts etc if you want to add those
>while you're in there.
I’m not in there any more.
-Alex
I’m not clear what was broken in Justin’s test. He mentioned that there was a
problem with RSLs, but RSLs are turned off by default and they do not really
offer any performance advantage using Apache Flex.
On Jan 21, 2015, at 10:36 AM, piotrz wrote:
> I agree with Justin. Once you build your a
On 21/01/15 08:43, Harbs wrote:
RSLs are turned off by default and they do not really offer any performance
advantage using Apache Flex.
It depends on your use case. If you update your app more often than
SDKs, you can give you users a smaller download after app updates, at
the cost of a lar
The License issue and maybe the copyright issue might be worth another RC.
I definitely apologize for missing those things earlier. I’m out of time
for tonight to try to reproduce RSL issue. The locale issue for Ant has
been there since we started using Ant.
I pushed my guess at how to fix the
Okay. Can you confirm that it’s broken?
On Jan 21, 2015, at 11:01 AM, Tom Chiverton wrote:
> On 21/01/15 08:43, Harbs wrote:
>> RSLs are turned off by default and they do not really offer any performance
>> advantage using Apache Flex.
> It depends on your use case. If you update your app more
The RSL 'issue' Justin reports isn't a regression, it's been around since 4.9...
"Looks like the file is question is named
"textLayout_4.14.0.20150121.swf" not the expected
"textLayout_20150121.swf".
The RSL in question has had the version number included since that
release: 'textLayout_4.9.1.144
Like I said; I have not been using RSLs since I switched to Apache Flex, so I
can’t comment one way or the other.
I guess it would be helpful if someone checks whether the behavior is actually
different.
On Jan 21, 2015, at 11:14 AM, Erik de Bruin wrote:
> The RSL 'issue' Justin reports isn't
It's just installed now :-)
The files have the same names as mentioned in the config files:
tchiverton@ev34:/tmp/apache-flex-sdk-4.14.0-bin$ find . -iname
'textLayout*swf'
./frameworks/rsls/textLayout_4.14.0.20150119.swf
tchiverton@ev34:/tmp/apache-flex-sdk-4.14.0-bin$ grep -Hrn
textLayout_4.
With a heavy heart, and very disappointed I'm canceling this RC.
Nearly all of us agreed to give the less-RC a fair chance. That
implied that all testing and vetting was to be done BEFORE an RC was
released. I have repeatedly asked if everyone would do so. I took the
lack of response to mean every
Cool.
I’d guess Justin’s issue was a Player trust file problem, and restarting Flash
Builder would probably fix that.
On Jan 21, 2015, at 11:30 AM, Tom Chiverton wrote:
> It's just installed now :-)
>
> The files have the same names as mentioned in the config files:
>
> tchiverton@ev34:/tmp/
I've cancelled the vote, and I've re-enabled the RC nightly builds. In
about 2 hrs. Alex's changes to the legal docs and build scripts should
be available for testing.
I will cut a new RC as soon as I have confirmation about the remaining
issues have been satisfactorily addressed.
EdB
On Wed,
On 21/01/15 09:33, Erik de Bruin wrote:
With a heavy heart, and very disappointed I'm canceling this RC.
Seems a bit rash to declare it a failure. I've only been looking at the
RSL issue for five minutes !
There were degrees of them being broken I'd accept as releasable, for
instance.
Tom
I'm told the license issues need fixing before we can release, or we
risk legal repercussions.
Since we can't make changes to an already published RC, I need to
cancel this one and create a new one. This waste of time is why the
'less-RC' release process was created. But not everyone agreed with
t
Hi,
> Seems a bit rash to declare it a failure.
Likewise. These issues should be discussed and what fixes (if any) are
required, and other people given the chance to test the SDK before cancelling
the vote, and people can be convinces to change their vote (although in this
case the issues ar
> There are still more testing that could be done re the new features and
> possibly (but hopefully not) other issues we may discover before we make a
> release.
Are you intentionally trying to misrepresent the 'less-RC' process? We
just spend 2 months testing the new features and other issues
Hi,
> Since we can't make changes to an already published RC, I need to
> cancel this one and create a new one.
Sure but further testing by the PMC on this RC may remove the need for further
RCs beyond the next one. Given the time passed since the last release and the
number of changes and new
Hi,
> Are you intentionally trying to misrepresent the 'less-RC' process?
Of course not, but we need as many RC as we need to get it right. The aim is
fewer RCs and while the idea number would be one that's IMO going to be hard to
achieve in practise. For whatever reason people only check in de
> Sure but further testing by the PMC on this RC may remove the need for
> further RCs beyond the next one.
The nightly RC builds are identical to the RC and have been available
for testing for over 2 months. The issues you reported were present in
all of these builds.
Had you bothered to set as
Thanks for the feedback, Piotr.
I added a message to the assertTrue call (see my commit just a few minutes ago).
However, from what I can tell there's nothing I can check for in
assertTrue, because I just want to make sure that no fatal error has
been thrown, which validates that the bug is not t
In my tests if I add an argument < 0 (in fact, < 1), the stack trace
of the RTE comes out with "at flash.display::BitmapData/ctor()", as I
mentioned. So I assumed that when the stack trace doesn't include the
ctor() function (which I guess is the C constructor) the cause is
different (most likely m
>> Are you intentionally trying to misrepresent the 'less-RC' process?
>
> Of course not, but we need as many RC as we need to get it right. The aim is
> fewer RCs and while the idea number would be one that's IMO going to be hard
> to achieve in practise. For whatever reason people only check in
I just tried this and it works! It's not the easiest process, but at
least there is a way to do it.
Thanks for chasing this, Fréd!
PS: I think your email client keeps adding "Re :" even when the
message subject already has "Re:" in it, which, at least for me in
Gmail, splits the conversation into
Tom, I hope you got this to work. Once you manage to log into FishEye,
the Jira commits panel should work.
On 9 January 2015 at 16:06, Tom Chiverton wrote:
> On 09/01/15 15:40, Frédéric THOMAS wrote:
>>>
>>> so I click that, but it doesn't believe the password I just
>>> entered to create the acc
flex-sdk_release-candidate - Build #76 - Successful
Changes since last build:
[jmclean] Update copyright year
[Alex Harui] remove prompt for OSMF download
[Alex Harui] move saxon9 to category b
[Alex Harui] add Batik fork W3C to LICENSE
[Alex Harui] add CONTRIBUTORS file to package
[Alex Haru
Hi,
> Had you bothered to set aside your pride and follow the 'less-RC' process
Please refrain from being rude on this public list. I'll think you'll agree
I'm not the only person responsible for checking release candidates and that
any PMC member could of found those issues, including yoursel
RSLs still have a valuable purpose depending on how many applications you host
out of one domain.
-Mark
-Original Message-
From: Harbs [mailto:harbs.li...@gmail.com]
Sent: Wednesday, January 21, 2015 3:44 AM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Release Apache Flex 4.14.0
I
It looks great, thanks for it. I just made a couple of cosmetic
changes to it. Now I'll go on to debug the still failing
FLEX_34625_Tests.as.
On 7 January 2015 at 11:25, Erik de Bruin wrote:
> Mihai,
>
> Thanks for taking the effort to figure out how to automate the
> FlexUnit tests using the new
Hi Mihai,
Does it mean it was easy for you to manage to log into FishEye ?Can you confirm
it works easily once log out / into Jira ?
I reported back to Atlassian the difficulty to connect thru those steps and
they delegated the issue, I'm waiting for their feedback.
Frédéric THOMAS
> From: miha
Yes, I just had to create a FishEye account, then log into it (for
some reason, after creating an account on FishEye it showed me the
commits - not in Jira, but in FishEye -, but I was still not logged
in), and then go back to Jira, refresh the ticket and click on
commits. This showed me the correc
I've just tried to compile with newest RC some app. In the installer I choose
FP 16, but in Intellij IDEA I see only FP 15. I'm getting error during the
compilation:
unable to open 'C:/sdks/Apache Flex 4.14
RC/frameworks/libs/player/15.0/playerglobal.swc'
I see in the frameworks/libs/player/16.0/
Ok, sounds good.
Either it was a temporary issue or they fixed it and I haven't got the feedback
yet.
Can someone else try the same ?
Thanks for reporting.
Frédéric THOMAS
> From: mihai.ch...@gmail.com
> Date: Wed, 21 Jan 2015 11:56:47 +
> Subject: Re: Re : Re: FishEye accounts
> To: dev@fle
Hi,
Just to make sure this doesn't get lost in the static of the failed RC
discussion: I've reset the release process to a pre-RC state.
In accordance with the new release policy, this is the time to test
the release. All aspects of it. To test the SDK, download the latest
RC nightly build using
Yep, I've been trying to debug that.
In parallel I've also been trying to do the same for Squiggly, and
while I did get a unit test to run (with some tweaks which I'll commit
when I'm done), now the usual ant build script fails for Squiggly.
That's because now it's also parsing the unit test (whic
> My question is: how does the apache project compile, despite there
> being a unit test in
> frameworks\projects\apache\src\tests\promises\cases\PromisesBasicTests.as?
I think the framework projects only build classes included in the
"*Classes.as" file in the root of the project (and their depend
I'm sorry guys this was some issue with Intellij IDEA.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p44468.html
Sent from the Apache Flex Development mailing
Erik, is it possible for me to get permissions to run the
flex-sdk_test job on demand? It's really difficult to debug the unit
test if I have to wait ~30 min after a commit to see the results. (My
username on Jenkins is mihaic.)
On 21 January 2015 at 15:13, wrote:
> Repository: flex-sdk
> Update
Thanks for the pointer, it allows me to make some steps forward.
On 21 January 2015 at 13:41, Erik de Bruin wrote:
>> My question is: how does the apache project compile, despite there
>> being a unit test in
>> frameworks\projects\apache\src\tests\promises\cases\PromisesBasicTests.as?
>
> I thin
> Erik, is it possible for me to get permissions to run the
> flex-sdk_test job on demand? It's really difficult to debug the unit
> test if I have to wait ~30 min after a commit to see the results. (My
> username on Jenkins is mihaic.)
I have sent the credentials to your private email address.
E
On 1/21/15, 2:41 AM, "Mihai Chira" wrote:
>In my tests if I add an argument < 0 (in fact, < 1), the stack trace
>of the RTE comes out with "at flash.display::BitmapData/ctor()", as I
>mentioned. So I assumed that when the stack trace doesn't include the
>ctor() function (which I guess is the C
On 1/21/2015 8:34 PM, Erik de Bruin wrote:
In accordance with the new release policy, this is the time to test
the release. All aspects of it. To test the SDK, download the latest
i suppose i haven't been paying enough attention but this test version doesn't
include the remoting, etc. bits? d
No, the test version is a complete SDK. It is what will become v.
4.14. The remoting etc. is a part of it.
EdB
On Wed, Jan 21, 2015 at 5:09 PM, Paul Hastings wrote:
> On 1/21/2015 8:34 PM, Erik de Bruin wrote:
>
>> In accordance with the new release policy, this is the time to test
>> the rele
All right, I've made a few changes to the way tests are run in order
to support [1].
One question: can someone with a black belt in ant help me reduce the
duplication between the '-test-run-execute' and
'-test-run-execute-with-extra-lib' tasks in flexunit-tests.xml?
Thanks!
[1] https://issues.apa
In fact, new to 4.14 is that the remoting code the Installer used to ask
you about is now based on the BlazeDS code donated to Apache Flex, so the
Installer no longer has to ask.
And while we were removing the remoting license checkbox, we found that we
may have mis-read policy and didn’t need to
On 1/21/15, 5:34 AM, "Erik de Bruin" wrote:
>
>In accordance with the new release policy, this is the time to test
>the release. All aspects of it. To test the SDK, download the latest
>RC nightly build using the Installer (right click, "Show Dev Builds",
>4.14 RC). If you want to check the rele
flex-sdk_release-candidate - Build #77 - Successful
Changes since last build:
[Alex Harui] clean up rat on build server. It picked up stuff from the BlazeDS
Maven build
[Alex Harui] allow a -Dnightly= flag on Approval script so it can run against
nightly rcs
For more information, check the c
I'm really struggling with this, if anyone can help (debugging why
FLEX_34625_Tests.as is failing).
The progress I made was:
-found out that UIImpersonator.testDisplay is a Sprite (when running
the unit test in IntelliJ, it's always an mx.core.Container instance,
which is fine).
-noticed that Flex
flex-sdk_release-candidate - Build #78 - Failure
Changes since last build:
[Alex Harui] tweak license
[Alex Harui] try to fix javascript packaging on Windows (worked ok on mac)
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candi
Alex, you missed the closing tag :-)
EdB
On Wednesday, January 21, 2015, wrote:
> Repository: flex-sdk
> Updated Branches:
> refs/heads/release4.14.0 00b786df1 -> 6cd0c686f
>
>
> try to fix javascript packaging on Windows (worked ok on mac)
>
>
> Project: http://git-wip-us.apache.org/repos/
Github user asfgit closed the pull request at:
https://github.com/apache/flex-sdk/pull/14
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Hi Kevin,
I've just pushed your fix into develop branch. Probably tomorrow we will
have this in Nightly Build of SDK.
I don't know whether Erik decide pickup this into 4.14 release. Test it
tomorrow in your application and let me know.
Thank you for this Fix!
Piotr
-
Apache Flex PMC
pio
flex-sdk_release-candidate - Build #79 - Fixed
Changes since last build:
[Alex Harui] missed closing the tag
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/79/.
Hi,
Re the LICENSE changes. I've not had time to investigate in detail but I would
assume the dtd's are under the W3C documentation license [2] not the software
one as they are defined in the W3C recommendation. [2][3] Do we know what
version of SVG the version of Bartik we bundles supports?
T
Mihai,
I think you have to set haltonfailure=true or verbose=true in your ant
flexunit target. The you will get full report.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Re-2-3-git-commit-flex-sdk-r
It was pretty confusing, so please double-check my sequence of logic:
1) I opened svg10.dtd
2) It had a link in the header [4]
3) That page had a link about “document use” [5]
4) On that page, which is the Document license, it said:
"The software or Document Type Definitions (DTDs) associated wit
If you specify a width / height for the spark:busyindicator the
RotationMatrix is calculated incorrectly.
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"
minWidth="955"
mi
Hi,
> It was pretty confusing, so please double-check my sequence of logic:
It's certainly not 100% clear.
> 4) On that page, which is the Document license, it said:
>
> "The software or Document Type Definitions (DTDs) associated with W3C
> specifications are governed by the Software Notice
>
On 1/21/2015 11:46 PM, Alex Harui wrote:
In fact, new to 4.14 is that the remoting code the Installer used to ask
you about is now based on the BlazeDS code donated to Apache Flex, so the
Installer no longer has to ask.
ah that was it. thanks for clearing that up.
And while we were removing t
On 1/21/15, 2:30 PM, "Justin Mclean" wrote:
>
>
>The copyright in the Java file (1999) may be an earlier version of the
>license. [1]
You mean sources/org/w3c/css/sac/LexicalUnit.java?
Actually, there are several java files that have W3C headers, and I think
all but LexicalUnit point to the 2
Hi,
To reproduce the RSL issue:
1. get the source package
2. compile as per README by:
ant main
ant frameworks-rsls
3. Turn into IDE by running:
ant -f installer.xml
The issue is with the flex config XML file and the RSL entries.
For instance if you followed the READEME i
Which theme/skin are you using?
On 1/21/15, 2:07 PM, "rodneyh" wrote:
>If you specify a width / height for the spark:busyindicator the
>RotationMatrix is calculated incorrectly.
>
>http://ns.adobe.com/mxml/2009";
> xmlns:s="library://ns.adobe.com/flex/spark"
>
Update: Interestingly, the RC Nightly does not build correctly. The build
machine is having character set issues. Pardon the extra builds while I
get that ironed out.
The implication of this is that nobody ever tried to run a build on the RC
nightly’s source package. I know I didn’t, I had been
> To reproduce the RSL issue:
> 1. get the source package
> 2. compile as per README by:
> ant main
> ant frameworks-rsls
> 3. Turn into IDE by running:
> ant -f installer.xml
>
> The issue is with the flex config XML file and the RSL entries.
What is the difference between
flex-sdk_release-candidate - Build #80 - Successful
Changes since last build:
No changes
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/80/.
Installer.xml is probably expecting some properties to match up. It was
designed to work with the binary package generated in the same run that
creates the source package.
How many folks are actually going to use the source package and need RSLs?
-Alex
On 1/21/15, 10:23 PM, "Erik de Bruin" wro
> How many folks are actually going to use the source package and need RSLs?
A very, very tiny number... But since we're in a holding pattern until
Justin approves the entire licensing and legal documentation setup for
4.14, we might as well give this a go.
EdB
--
Ix Multimedia Software
Jan
70 matches
Mail list logo
