On 4/20/13 10:48 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
Rather than keeping them as Later perhaps change to Won't fix and add a
comment Old issue put on hold by Adobe. Please re-open if you run into this
issue or think it's important.?
I'm ok with that too, but I think
Hi,
Thanks. Do you have time to add some more tests?
Added 40 odd tests to check various formats and check invalid inputs.
https://git-wip-us.apache.org/repos/asf?p=flex-sdk.git;a=commitdiff;h=531f7f2fe7aa72fa3c998d76c2de7b9b1761ee03
All test pass.
If anyone can suggest other tests go ahead
Hi,
I've been looking at DataField and it has a few problems mostly how it dealing
with format string parsing in stringToDate and dateToString static methods.
There are several unresolved JIRA issues around this component.
Some of the issues include.
1. Poor support of M and D vs MM and DD
.
There are several unresolved JIRA issues around this component.
Some of the issues include.
1. Poor support of M and D vs MM and DD. Currently:
1/10/2013 formatted with D/M/YY = null
1/10/2013 formatted with D/MM/YY = null
1/10/2013 formatted with M/D/YY = null
7/17/69 formatted with M/D/YY = null
1
Hi,
Thanks. Do you have time to add some more tests?
Mastella test no as I'm not 100% familiar with them yet.
I tested locally with about 50 combinations of formats and dates. I run against
4.9 and 4.10 and diffed the trace output to see what had changed.
Here the rough test code I used -
-16396
[2] https://bugs.adobe.com/jira/browse/SDK-11282
-Mark
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Tuesday, April 16, 2013 11:17 PM
To: dev@flex.apache.org
Subject: Re: [Discuss] Old imported JIRA issues
I had to write my own export/import tool because Adobe
Hi,
However I did personally test the code given and it produced correct results.
Put the test code into JIRA if you can - means someone can easily retest if
needed at a future date.
Thanks,
Justin
The very old JIRA issues imported from Adobe are missing attachments (can
go to original adobe bug and find some of them). But more importantly,
there are a few that have comments from the import like[1]... If the
comments say the original resolution is fixed. Can we mark the issue fixed
on our
Forgot to leave an example URL [1]. There are a total of 28 more of them
that I could knock out if so.
[1] https://issues.apache.org/jira/browse/FLEX-15274
On Tue, Apr 16, 2013 at 8:01 PM, Mark Kessler
kesslerconsult...@gmail.comwrote:
The very old JIRA issues imported from Adobe are missing
Hi,
The very old JIRA issues imported from Adobe are missing attachments (can
go to original adobe bug and find some of them).
It's a know issue - infra and Alex have been working on it for some time.
But more importantly,there are a few that have comments from the import
like[1
...@classsoftware.comwrote:
Hi,
The very old JIRA issues imported from Adobe are missing attachments (can
go to original adobe bug and find some of them).
It's a know issue - infra and Alex have been working on it for some time.
But more importantly,there are a few that have comments from the import
like[1
or easytest so other
committers/users can help out.
Some issues would be very easy to validate, for instance:
https://issues.apache.org/jira/browse/FLEX-26698 - Currency format issue
when formatting 0
https://issues.apache.org/jira/browse/FLEX-20322 - French locale issue
with month names
I had to write my own export/import tool because Adobe is on an older and
highly customized version of JIRA, and we also had to filter out security
related issues. It is entirely possible there were bugs in it. But the
issue you posted here does look closed to me. Am I missing something, or
can
point me to another issue?
Think that issue is actually closed and fixed but try this list:
https://issues.apache.org/jira/issues/?filter=12323883
Justin
...@adobe.com wrote:
I had to write my own export/import tool because Adobe is on an older and
highly customized version of JIRA, and we also had to filter out security
related issues. It is entirely possible there were bugs in it. But the
issue you posted here does look closed to me. Am I
Hi,
I wonder if there's a way to mass update all of those issues?
Yes JIRA can do that but what do you want changed?
The only minor issue I see is the Original Resolution: Fixed text in the
comments but the JIRA issue itself is in the correct state.
Justin
On Apr 16, 2013 8:40 PM, Alex Harui aha...@adobe.com wrote:
OK, in a quick sample, open-but-fixed-in-the-comments seems to be mapping
to
status=community or status=internalreview, which means that these are not
fixed.
I wonder if there's a way to mass update all of those issues?
-Alex
On 4/16/13 8:45 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
I wonder if there's a way to mass update all of those issues?
Yes JIRA can do that but what do you want changed?
The only minor issue I see is the Original Resolution: Fixed text in the
comments but the JIRA issue
HI,
Please turn off email notifications when doing mass updates.
If you referring to the easyfix/easytest tags that are individual edits and not
considered a mass update. There's no way to turn email notification off for a
tag edit field that I know of.
Should only be a dozen or so more.
On Apr 16, 2013 8:56 PM, Justin Mclean jus...@classsoftware.com wrote:
HI,
Please turn off email notifications when doing mass updates.
If you referring to the easyfix/easytest tags that are individual edits
and not considered a mass update. There's no way to turn email notification
off for
Hi,
When we received the JIRA bugbase from Adobe it contained a lot of old
unresolved issues from earlier versions of the SDK.
I've gone though and marked some of these issue with easytest if they would
be easy to test and easyfix if I think they would be easy to fix or patch.
You can see
to existing issues, new issues etc etc so probably not
realistically possible.
All done now (for now) BTW.
Justin
Cyrill Zadra created FLEX-33494:
---
Summary: Migrate open jira issues from adobe
Key: FLEX-33494
URL: https://issues.apache.org/jira/browse/FLEX-33494
Project: Apache Flex
Issue Type: Sub-task
could make lives easier for committers by generating patches and
attaching them to JIRA.
Also, generating patches would force you to set up your sdk folders, etc.
in the right way. As you start working on more complicated issues that
touch a number of files, the process becomes easier to manage
Hi,
I wonder if we can turn off email notifications before you do that and then
turn them back on after?
Yes you can turn email notification off for bulk changes in JIRA.
Justin
sdk folders, etc.
in the right way. As you start working on more complicated issues that
touch a number of files, the process becomes easier to manage for you.
And last but not least, if you keep contributing, you will be invited to
become a committer at which point you wont have to worry
Thanks Chris.
-Message d'origine-
From: christofer.d...@c-ware.de
Sent: Monday, March 11, 2013 9:32 AM
To: dev@flex.apache.org
Subject: AW: Maven JIRA issues
Well I just checked them and closed some of them. But most of the Maven
issues simply used the Word Maven when discribing
Check out the Squashing Bugs section on our website :
http://flex.apache.org/community-getinvolved.html
Essentially, you add a patch to the ticket, and we put them in for you
(after a review). More (good) patches give you karma and will get you
voted in to be a committer.
-Nick
On Mon, Mar 11,
into this
Getting Issues While Compiling the automation.swc and automation_dmv.swc
-
Key: FLEX-33424
URL: https://issues.apache.org/jira/browse/FLEX-33424
Project: Apache Flex
Issue
No. A locked file error.
Any work I was doing, was outside the working copy, so nothing should be lost…
On Mar 11, 2013, at 9:24 PM, Om wrote:
Is the error something about TLF? If so, there is an easy way to fix it.
That way you wont lose your work.
And btw, you could also create a patch
[
https://issues.apache.org/jira/browse/FLEX-33070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean resolved FLEX-33070.
--
Resolution: Fixed
Mustella build file issues
Hi,
There's about a dozen or so outstanding Maven issues. Can someone more familiar
with Maven (I don't use it) take a look and see if any of the JIRA issues can
be resolved and/or clarify what the progress is.
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLEX%20AND%20text%20
that are relatively easy to fix.
https://issues.apache.org/jira/issues/?filter=12322826
There are about 16 issues that are currently unassigned. Anyone we wiling
to take any of these on?
Thanks,
Justin
Hi,
I can take a look at them. I didn't troll those Easy to fix in hopes
that some other community members might take them on, but it's probably
best to get them out the door.
Yep I was hoping some of the less active committer or people looking to be
committers would pick them up, but if we
Hi,
There a large number of issue assigned to Adobe JIRA. I'm assuming there were
issue that were assign when the JIRA issue were imported. Who if anyone should
they be assigned to?
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLEX%20AND%20resolution%20%3D%20Unresolved%20AND
Not sure why they got assigned. IMO, unless you are actively working on an
issue, issues should be unassigned.
On 3/10/13 8:56 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
There a large number of issue assigned to Adobe JIRA. I'm assuming there were
issue that were assign when
On 3/10/13 9:14 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
Not sure why they got assigned. IMO, unless you are actively working on an
issue, issues should be unassigned.
Fixed we now have 61 new unassigned issues.
Ooh! That's so exciting! Seriously, though, thanks
I am having dev and users at flex.apache.org mailing list issues. I
subscribed to the users mailing list for both groups but I am no longer
receiving emails from either the developer list or the users list for flex.
Are there any issues with the subscription site? I have pinged our ITS
Hi Margo,
I just checked the dev list. You are shown as being subscribed. When you
re-subscribed, I assume you got emails from the robot?
-Alex
On 2/27/13 9:13 AM, Margo Powell mmpow...@ad.unc.edu wrote:
I am having dev and users at flex.apache.org mailing list issues. I
subscribed
The addresses changed back in January. It is possible you were filtering
for flex-...@incubator.apache.org instead of dev@flex.apache.org?
-Nick
On Wed, Feb 27, 2013 at 12:13 PM, Margo Powell mmpow...@ad.unc.edu wrote:
I am having dev and users at flex.apache.org mailing list issues. I
?
-Nick
Original Message
Subject:email issues?
Date: Wed, 27 Feb 2013 12:13:18 -0500
From: Margo Powell mmpow...@ad.unc.edu
To: dev@flex.apache.org, us...@flex.apache.org
I am having dev and users at flex.apache.org mailing list issues. I
subscribed
I just successfully signed up with my personal account. Ignore the previous
noise please - I will have our campus ITS group investigate further why all
these emails are being blocked on my work email address.
Thanks for your help
RegardsMargo Powell
OK, but FWIW, the previous email I sent to you that you seemed to have
received was sent via dev@. How did you know I sent it? Were you watching
the archives or something else?
On 2/27/13 1:53 PM, Margo Powell margopow...@msn.com wrote:
I just successfully signed up with my personal account.
I was watching the archives
viahttp://markmail.org/search/+list:org.apache.incubator.flex-dev
I never received anything via dev@
Thanks again Margo
From: aha...@adobe.com
To: dev@flex.apache.org
Date: Wed, 27 Feb 2013 13:58:17 -0800
Subject: Re: email issues?
OK, but FWIW, the previous
[
https://issues.apache.org/jira/browse/FLEX-33148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
OmPrakash Muppirala closed FLEX-33148.
--
Fix accessibility issues as suggested by Carol (and Adobe's accessibility
expert
Carol Frampton created FLEX-33342:
-
Summary: Installer README addition for certificate issues
Key: FLEX-33342
URL: https://issues.apache.org/jira/browse/FLEX-33342
Project: Apache Flex
Issue
401 - 446 of 446 matches
Mail list logo
