[
https://issues.apache.org/jira/browse/FLEX-33547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671239#comment-13671239
]
Erik de Bruin commented on FLEX-33547:
--
Resolved:
FLEX-33501
FLEX-33451
FLEX-33535
Ok, the job on the Jenkins job (Window Azure) is nearly done... A
single '-all' run takes around 9 hours to complete, so I've added a
schedule that does 2 runs each day.
I've started a '-all' run and added this list to the recipients of the
failure emails. I expect there will be some in the days
This vote is on the following proposal:
Create a list: j...@flex.apache.org. All JIRA emails generated by
https://issues.apache.org/jira/browse/FLEX will go only to the new
list. jira@f.a.o will function the same as commits@f.a.o. - people
subscribe themselves and the 'reply-to' is dev@f.a.o, so
+1
Will be happy to be able to filter the messages apart from the dev messages
more easily.
-Mark
-Original Message-
From: Erik de Bruin [mailto:e...@ixsoftware.nl]
Sent: Friday, May 31, 2013 6:47 AM
To: dev@flex.apache.org
Subject: [VOTE] Let's move JIRA emails to a new list
This
+1
On Fri, May 31, 2013 at 6:54 PM, Kessler CTR Mark J
mark.kessler@usmc.mil wrote:
+1
Will be happy to be able to filter the messages apart from the dev messages
more easily.
-Mark
-Original Message-
From: Erik de Bruin [mailto:e...@ixsoftware.nl]
Sent: Friday, May 31,
+1
2013/5/31 Cyrill Zadra cyrill.za...@gmail.com
+1
On Fri, May 31, 2013 at 6:54 PM, Kessler CTR Mark J
mark.kessler@usmc.mil wrote:
+1
Will be happy to be able to filter the messages apart from the dev
messages more easily.
-Mark
-Original Message-
From: Erik
+1
~a~
www.ayobinitie.com
http://mrbinitie.blogspot.com
On 31 May 2013 11:08, Carlos Velasco carlos.velasco.bla...@gmail.comwrote:
+1
2013/5/31 Cyrill Zadra cyrill.za...@gmail.com
+1
On Fri, May 31, 2013 at 6:54 PM, Kessler CTR Mark J
mark.kessler@usmc.mil wrote:
+1
+1
On Fri, May 31, 2013 at 6:46 AM, Erik de Bruin e...@ixsoftware.nl wrote:
This vote is on the following proposal:
Create a list: j...@flex.apache.org. All JIRA emails generated by
https://issues.apache.org/jira/browse/FLEX will go only to the new
list. jira@f.a.o will function the same
+1 (binding)
-Message d'origine-
From: Erik de Bruin
Sent: Friday, May 31, 2013 12:46 PM
To: dev@flex.apache.org
Subject: [VOTE] Let's move JIRA emails to a new list
This vote is on the following proposal:
Create a list: j...@flex.apache.org. All JIRA emails generated by
Hi,
+1 (binding)
Would prefer it be called issues@f.a.o in line with other Apache projects.
Justiin
+! Binding
On 5/31/2013 8:24 AM, Frédéric THOMAS wrote:
+1 (binding)
-Message d'origine- From: Erik de Bruin Sent: Friday, May 31,
2013 12:46 PM To: dev@flex.apache.org Subject: [VOTE] Let's move JIRA
emails to a new list
This vote is on the following proposal:
Create a list:
+1 binding (technically I've already been filtering them with gmail but
this will be good)
On Fri, May 31, 2013 at 8:33 AM, Jeffry Houser jef...@dot-com-it.comwrote:
+! Binding
On 5/31/2013 8:24 AM, Frédéric THOMAS wrote:
+1 (binding)
-Message d'origine- From: Erik de Bruin
+1
Harbs
+1
-Ursprüngliche Nachricht-
Von: Harbs [mailto:harbs.li...@gmail.com]
Gesendet: Freitag, 31. Mai 2013 16:12
An: dev@flex.apache.org
Betreff: Re: [VOTE] Let's move JIRA emails to a new list
+1
Harbs
+1 (non-binding - community)
On May 31, 2013, at 4:46 AM, Erik de Bruin e...@ixsoftware.nl wrote:
This vote is on the following proposal:
Create a list: j...@flex.apache.org. All JIRA emails generated by
https://issues.apache.org/jira/browse/FLEX will go only to the new
list. jira@f.a.o
Was there really a -u? Any idea what that was from? In
mustella/test_changes.sh I have a test for a non-empty failures.txt that
seems to be working for me.
If failures.txt does not exist or is empty, -failures will run all tests.
I suppose we should fix that, but in general -failures should not
+1
Note that it looks like we are not auto-subscribing folks, but IMO
subscribing is required for committers.
On 5/31/13 3:46 AM, Erik de Bruin e...@ixsoftware.nl wrote:
This vote is on the following proposal:
Create a list: j...@flex.apache.org. All JIRA emails generated by
Hello, everyone.
My name is Tony Compton, a developer for HP Exstream, a division of
Hewlett-Packard, Inc. I've spent the last year working on a product that relies
on Flex and TLF. I'm writing today because I work with TLF almost daily and I
would like to help contribute to the project, but
I know little to nothing about the kung-fu of bash/sh, so I picked up
this snippet from the interwebs (it's currently commented out in
'jenkins.sh' on the Azure instance:
if [[ -s failures.txt ]] ; then
echo Some tests failed: running '-failures'
./mini_run.sh -failures
else
echo All tests
Yeah, I'm no bash expert either. Each character seems to have importance.
I looked at test_changes.sh and it only has one set of [] instead of two.
Not sure if that would make a difference or not.
if [ -s failures.txt ] ; then
On 5/31/13 8:54 AM, Erik de Bruin e...@ixsoftware.nl wrote:
Sounds reasonable to me. Create a JIRA issue with a patch for the changes
you want and we'll try to get a committer to review and commit it.
On 5/31/13 7:36 AM, Compton, Tony anthony.ste.comp...@hp.com wrote:
Hello, everyone.
My name is Tony Compton, a developer for HP Exstream, a division of
I'd like to vote in favor, but I'm not liking the quantity of -1's we're
seeing.
Can we cancel this vote and draft a more detailed proposal, maybe after
some discussing with those voting -1?
I think the new proposal should be explicit about the name of the repo.
I think the new proposal should
Tony,
This is very cool. We seem to lack a contributor that knows TLF, so
you if you can help, that would be awesome.
As Alex indicated, create a JIRA issue for each of your suggested
changes/enhancements, describe in them the thing you're trying to
solve and attach a patch to it that has the
Alex, even if AOP would be added at compiling time, it would be up to the
frameworks to leverage it, swiz or other.
Regarding -1 votes, I think 2 of them will be solved if swiz is under the
utilities and not making it as part of the Flex SDK.
The last -1, no reason has been given so Igor will
The -1 people (3, of whom 2 have a binding vote) have declined to
respond to repeated requests for clarification (by both Justin and
me). Their previous comments seem to indicate they don't want Swiz to
become part of the SDK. The VOTE proposal clearly states:
This will be a project like flexunit
The thing I don't fully understand is this:
Swiz is already licensed under the Apache License (
https://github.com/swiz/swiz-framework/blob/develop/LICENSE ). If people
want to contribute, use, or modify then what is stopping them?
How will bringing the Swiz framework into the Apache
For me, I think the main advantage for both projects is: exposure.
EdB
On Fri, May 31, 2013 at 6:56 PM, Jeffry Houser jef...@dot-com-it.com wrote:
The thing I don't fully understand is this:
Swiz is already licensed under the Apache License (
The problem is that there are a few contributors that never got their
improvements / bug fixes merged to the project so anyone using swiz is
missing those.
On 31 May 2013 17:56, Jeffry Houser jef...@dot-com-it.com wrote:
The thing I don't fully understand is this:
Swiz is already licensed
Same concerns here. Reviving Swiz would be a good thing to do, but if
that happens under the Apache Flex flag it could be recognized as 'the
best' or 'supported' IoC framework, even if explicitely stated
otherwise. It might be better to keep the Status Quo (none of those
frameworks in Apache Flex)
If swiz is donated and end up under the utilities, how would it differ from
FlexUnit donation? Why would be swiz assumed as the best or supported
framework and not FlexUnit? I would welcome any other lib, IoC or not to
Apache Flex contrib, if it would make easier to the community to keep it
alive
I was thinking that by being more explicit and proposing a contrib repo
that is intended as a warehouse for low-activity items it would help
resolve some of these misunderstandings. FlexUnit and the installer in
utilities are still more active, IMO.
I'm just concerned about wrapping up the vote
For me, it is a +1 for the sentiment. But an overall -1 for the lack of
specifics in the proposal.
Here are the things that are bothering me:
1. We havent heard from the original developer that he/she wants to donate
this code. Were they supposed to mail on this list? Are they going to
stay
See https://builds.apache.org/job/flex-sdk_asdoc/14/changes
Changes:
[aharui] script to test changes noted in 'git status'
[aharui] don't send mail if there isn't an email address parameter
[aharui] Flex-33450 DataGrid RTE
[jmclean] Added link to AIR SDK for linux.
[jmclean] Fix for older
Tony,
I just want to echo Erik's sentiments on this. As you can see, there has
not been much activity in the TLF library after the donation to Apache.
Whatever work you can do to improve it and bring more attention to it,
that would be great. I will be glad to help you as well.
Thanks,
Om
On
See http://localhost:8080/job/flex-sdk_mustella/119/
--
[...truncated 79789 lines...]
[java] spark/validators/NumberValidator/Methods/NV_validate_tester
NV_validate_default_valid_model_test18 Passed
[java]
+1 binding
Alex, since that was the controversial part of the proposal, perhaps it is
better to have a separate vote for it.
Thanks,
Om
On May 31, 2013 8:45 AM, Alex Harui aha...@adobe.com wrote:
+1
Note that it looks like we are not auto-subscribing folks, but IMO
subscribing is required
Erik,
Do you know if you pulled down the png.xml files before this run. This
list contains many of the png.xmls I checked in last night.
If I don't hear from you in the next hour or so, I will try to log in and
look for myself.
-Alex
On 5/31/13 12:59 PM, flex.muste...@gmail.com
I just noticed there is more than one Apache Flex LinkedIn Group.
http://www.linkedin.com/groups/Apache-Flex-Developers-4296888
http://www.linkedin.com/groups/Apache-Flex-4296644
Do we care?
Does Apache care from a branding perspective?
-Alex
Hi,
seems like all has been said yet. I don't think we should stop the vote
since as others commented two -1 votes was left in the cold with any
explanation or commenting one that was explicitly exposed in the starting
vote mail.
Seems that the only one problem that people said is that Swiz
Hi, I'm the owner. Please let me know of anything needs changed.
Aj
Sent from my iPhone
On May 31, 2013, at 6:45 PM, Alex Harui aha...@adobe.com wrote:
I just noticed there is more than one Apache Flex LinkedIn Group.
http://www.linkedin.com/groups/Apache-Flex-Developers-4296888
[
https://issues.apache.org/jira/browse/FLEX-21488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean reopened FLEX-21488:
--
Reported as an issue and now TLF is part of Flex we can change.
[TLF 2458351]
Hi,
This seems to already by an issue in Apache's Jira
(https://issues.apache.org/jira/browse/FLEX-21488) which is closed to be
tracked by the Adobe Jira, but it seems the Adobe Jira has already been
decommissioned. Perhaps we should open it back up-or maybe I'm missing
something.
I've
I'm going to try to log in in about 10 minutes unless I hear that someone
else is connected. I got connected earlier, but it seemed to hang up.
-Alex
On 5/31/13 3:04 PM, Alex Harui aha...@adobe.com wrote:
Erik,
Do you know if you pulled down the png.xml files before this run. This
list
I just logged in a minute ago, but I wasn't planning on doing anything
serious, so I won't touch the machine until you give me the all clear
;-)
And I did pull the latest before the last run.
EdB
On Sat, Jun 1, 2013 at 6:35 AM, Alex Harui aha...@adobe.com wrote:
I'm going to try to log in in
See https://builds.apache.org/job/flex-sdk_asdoc/15/
OK, I logged in, but it was running mustella which means that the data I'm
looking for was gone. I did confirm that the png.xml files are there,
which is a bit disturbing, since that should have fixed many of these
failures.
This weekend, my opportunities to look at it will be around this time
Alex, the information you're looking for should still be available in
Jenkins, as it should keep the logs for the last 10 builds and the
logs contain basically results.txt.
If not, feel free to stop the running of a Jenkins job any time it
suits you. There's no use in running Mustella twice a day
Hi Erik,
It turns out we're at the point where I need the bad.png and bad.png.xml
files which get cleaned out at the start of the run.
Because my opportunities to look at it are limited this weekend, it would
be best if someone else can catch the end of a run and stop Jenkins. It
looked like it
I'll catch it in about 4 hours and stop the automated runs until you
have a chance to look at the results.
EdB
On Sat, Jun 1, 2013 at 7:15 AM, Alex Harui aha...@adobe.com wrote:
Hi Erik,
It turns out we're at the point where I need the bad.png and bad.png.xml
files which get cleaned out at
49 matches
Mail list logo
