janvier 2014 18:52
À : dev@flex.apache.org
Objet : Re: Anyone willing to help out with these regression / important
issues?
Ah ok. If ScrollableStageTextInputSkin works in RTL environments, that
would be great!
On 1/20/14 9:47 AM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
Alex, I
with these regression / important issues?
Hi,
We have a list of issues that need fixing for the 4.12 release anyone will to
help out and fix them? [1]
Thanks,
Justin
1. https://issues.apache.org/jira/browse/FLEX-33952
Hi,
We have a list of issues that need fixing for the 4.12 release anyone will to
help out and fix them? [1]
Thanks,
Justin
1. https://issues.apache.org/jira/browse/FLEX-33952
décembre 2013 01:26
À : dev@flex.apache.org
Objet : Re: strange issues in JIRA
Hi,
Yes, please.
Done + enjoy!
Thanks,
Justin
Didn't miss anything, really
-Message d'origine-
De : Cosma Colanicchia [mailto:cosma...@gmail.com]
Envoyé : vendredi 6 décembre 2013 14:41
À : Apache Flex Developers ML
Objet : Re: strange issues in JIRA
I was curious to read them, but I was late to the party :)
2013/12/6 Maurice
They were completely empty minus the title and a tag.
-Mark
-Original Message-
From: Cosma Colanicchia [mailto:cosma...@gmail.com]
Sent: Friday, December 06, 2013 8:41 AM
To: Apache Flex Developers ML
Subject: Re: strange issues in JIRA
I was curious to read them, but I was late
Hi
Most strange issues have been raised in JIRA:
https://issues.apache.org/jira/browse/FLEX-33979
https://issues.apache.org/jira/browse/FLEX-33980
Is this some sort of joke ?
If you don't see any objection, I will close them.
Maurice Amsellem
SYSTAR RD - BusinessBridgeFX
Wow, the guy has created two other equally dumb issues:
https://issues.apache.org/jira/browse/FLEX-33981
https://issues.apache.org/jira/browse/FLEX-33982
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 5 décembre 2013 23:39
À : dev
maurice.amsel...@systar.com wrote:
Wow, the guy has created two other equally dumb issues:
https://issues.apache.org/jira/browse/FLEX-33981
https://issues.apache.org/jira/browse/FLEX-33982
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : jeudi 5
, you can
close as duplicates against FLEX-33982 if that bug looks like it finally
got entered correctly.
-Alex
On 12/5/13 2:40 PM, Maurice Amsellem maurice.amsel...@systar.com
wrote:
Wow, the guy has created two other equally dumb issues:
https://issues.apache.org/jira/browse/FLEX-33981
Hi,
Give it an hour or so to see if they can work it out or ask for help on the
list.
I'd actually delete them than close them as they provide no useful information
(yet).
Thanks,
Justin
Hi,
Reporter: Samsung Galaxy Note
Boy, smartphones are getting smarter these days...
And that's how the singularity started :-)
Justin
I'd actually delete them than close them as they provide no useful information
(yet).
Sure.
Must be someone else, I do not have permission to delete issues (using JIRA
bulk change)
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : jeudi 5 décembre 2013
Would you like admin rights to JIRA? I can give them to you.
Yes, please.
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : vendredi 6 décembre 2013 00:40
À : dev@flex.apache.org
Objet : Re: strange issues in JIRA
Hi,
Must be someone else, I do
Hi,
Yes, please.
Done + enjoy!
Thanks,
Justin
:
Hi,
I am attempting to take the DataGrid, written in ActionScript, and
compile it into JavaScript to see if that's a viable way to build
JavaScript components - or at least get a good head start on writing
the
JavaScript. I've run into a couple of issues since taking the most
recent falcon code
it into JavaScript to see if that's a viable way to build
JavaScript components - or at least get a good head start on writing
the
JavaScript. I've run into a couple of issues since taking the most
recent falcon code changes.
Issue 1
My ActionScript code reads:
import org.apache.flex.core.IBeadModel;
Š
var
...@adobe.com wrote:
Hi,
I am attempting to take the DataGrid, written in ActionScript, and
compile it into JavaScript to see if that's a viable way to build
JavaScript components - or at least get a good head start on writing
the
JavaScript. I've run into a couple of issues since taking the most
on
writing
the
JavaScript. I've run into a couple of issues since taking the most
recent falcon code changes.
Issue 1
My ActionScript code reads:
import org.apache.flex.core.IBeadModel;
Š
var sharedModel:IDataGridModel = _strand.getBeadByType(IBeadModel)
as
IDataGridModel;
I get this error
...@ixsoftware.nl]
Sent: Wednesday, November 20, 2013 8:51 AM
To: dev@flex.apache.org
Subject: Re: [FALCONJX] [FLEXJS] AS to JS compilation issues
Yes, the latest thing: since the last compiler update we need Java 1.7,
I'm afraid.
EdB
On Wed, Nov 20, 2013 at 4:25 PM, Peter Ent p...@adobe.com wrote
: Wednesday, November 20, 2013 8:51 AM
To: dev@flex.apache.org
Subject: Re: [FALCONJX] [FLEXJS] AS to JS compilation issues
Yes, the latest thing: since the last compiler update we need Java 1.7,
I'm afraid.
EdB
On Wed, Nov 20, 2013 at 4:25 PM, Peter Ent p...@adobe.com wrote:
I rebuilt
just also move to 1.7 or not.
-Alex
- Gordon
-Original Message-
From: Erik de Bruin [mailto:e...@ixsoftware.nl]
Sent: Wednesday, November 20, 2013 8:51 AM
To: dev@flex.apache.org
Subject: Re: [FALCONJX] [FLEXJS] AS to JS compilation issues
Yes, the latest thing: since the last compiler
: Wednesday, November 20, 2013 8:51 AM
To: dev@flex.apache.org
Subject: Re: [FALCONJX] [FLEXJS] AS to JS compilation issues
Yes, the latest thing: since the last compiler update we need Java
1.7,
I'm afraid.
EdB
On Wed, Nov 20, 2013 at 4:25 PM, Peter Ent p...@adobe.com wrote:
I rebuilt
also move to 1.7 or not.
-Alex
- Gordon
-Original Message-
From: Erik de Bruin [mailto:e...@ixsoftware.nl]
Sent: Wednesday, November 20, 2013 8:51 AM
To: dev@flex.apache.org
Subject: Re: [FALCONJX] [FLEXJS] AS to JS compilation issues
Yes, the latest thing: since the last compiler update
Hi,
I am attempting to take the DataGrid, written in ActionScript, and compile it
into JavaScript to see if that's a viable way to build JavaScript components -
or at least get a good head start on writing the JavaScript. I've run into a
couple of issues since taking the most recent falcon
on writing the
JavaScript. I've run into a couple of issues since taking the most
recent falcon code changes.
Issue 1
My ActionScript code reads:
import org.apache.flex.core.IBeadModel;
Š
var sharedModel:IDataGridModel = _strand.getBeadByType(IBeadModel) as
IDataGridModel;
I get this error while
, written in ActionScript, and
compile it into JavaScript to see if that's a viable way to build
JavaScript components - or at least get a good head start on writing the
JavaScript. I've run into a couple of issues since taking the most
recent falcon code changes.
Issue 1
My ActionScript code reads
on writing the
JavaScript. I've run into a couple of issues since taking the most
recent falcon code changes.
Issue 1
My ActionScript code reads:
import org.apache.flex.core.IBeadModel;
Š
var sharedModel:IDataGridModel = _strand.getBeadByType(IBeadModel) as
IDataGridModel;
I get this error while
Hello all ,
I have created customize class that extends Arraycollection
For eg
Public class PagingArrayCollection extends Arraycollection
Now I have to cast ArrayCollection to PagingArrayCollection.
Suppose
Var arr: ArrayCollection = new ArrayCollection();
Var lst: PagingArrayCollection= new
arr is an instance of ArrayCollection, not an instance of
PagingArrayCollection
On 30 October 2013 17:49, Seema Makkar seema.mak...@aricent.com wrote:
Hello all ,
I have created customize class that extends Arraycollection
For eg
Public class PagingArrayCollection extends Arraycollection
You can cast a sub class to its super class, not the opposite
Maurice
-Message d'origine-
De : Seema Makkar [mailto:seema.mak...@aricent.com]
Envoyé : mercredi 30 octobre 2013 10:50
À : dev@flex.apache.org
Objet : Issues in Type casting
Hello all ,
I have created customize class
How should we specify bugs for things like FlexUnit when entering them in JIRA
to keep things a bit separate.
Maybe there is something obvious I missed... if not, ideas?
Mike
There is a JIRA version Apache FlexUnit 4.2.
Maybe an additional JIRA Component named FlexUnit would be helpful.
Cyrill
On 18.09.2013, at 19:46, Michael A. Labriola labri...@digitalprimates.net
wrote:
How should we specify bugs for things like FlexUnit when entering them in
JIRA to keep
Maybe an additional JIRA Component named FlexUnit would be helpful.
I think that's the right idea. Else you are immediately tying things to a
version and that's not the point of reporting a bug
Added a FlexUnit component.
On 9/18/13 11:55 AM, labri...@digitalprimates.net
labri...@digitalprimates.net wrote:
Maybe an additional JIRA Component named FlexUnit would be helpful.
I think that's the right idea. Else you are immediately tying things to a
version and that's not the point of
Hi,
May help if you looking for something to fix or want to help out with testing.
https://issues.apache.org/jira/issues/?filter=12324867
This is the list of unresolved issues than have been raised by someone and not
imported into JIRA from the old bugbase - there's only 280 of them!
Only
Hi,
Here's the list of the currently assign JIRA issues, I know that some are being
worked on and some may be resolved, but if you're assigned to an issue but are
no longer willing to work on it can you mark it as unassigned.
Adobe JIRA
FLEX-33580 CLONE - Ambiguous reference when using
Hi,
Just to put it into context 380 odd issues have been resolved from that same
set which means we've resolved about 60% of issues that people have raised. We
could probably do better but I'm reasonably sure that's better than resolution
rate of issues when Flex was with Adobe.
Thanks
tracking. The flash applet lets us get around those issues.
-Nick
On Thu, Aug 29, 2013 at 5:30 PM, Eric eh.fx...@gmail.com wrote:
Hello,
I had some minor issues with grabbing the SDK using Chrome (and IE).
Nothing to stop anyone serious, but some devs can be picky about first
impressions
Hello,
I had some minor issues with grabbing the SDK using Chrome (and IE).
Nothing to stop anyone serious, but some devs can be picky about first
impressions, and I want to see this SDK continue to grow like it should.
1) With Chrome (Version 29.0.1547.57 m), clicking the download link
On Aug 19, 2013 5:18 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
I vote for redirect or just a link to it from our site, like we do for
our
Markmail and Apache mailing lists archives.
Linking is no issue. The issue is how is a user going to remember or type
if needed those rather
Hi,
Both good news and bad news on the Nabbel front.
1. Infa wont add a CNAME for the domain names so we're stuck with the ugly
domain names.
Only solution I can see to this is make some pages that redirect there eg
flex.apache.org/formus/user or lex.apache.org/userforum
On 8/19/13 4:36 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
Both good news and bad news on the Nabbel front.
I don't have any karma re the mailing list someone mind giving it to me
so I can look into this?
I asked Infra to add you. Not clear that will give you enough powers.
You
On 8/19/13 5:02 PM, Alex Harui aha...@adobe.com wrote:
On 8/19/13 4:36 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
Both good news and bad news on the Nabbel front.
I don't have any karma re the mailing list someone mind giving it to me
so I can look into this?
I asked Infra to
On Mon, Aug 19, 2013 at 4:36 PM, Justin Mclean jus...@classsoftware.comwrote:
Hi,
Both good news and bad news on the Nabbel front.
1. Infa wont add a CNAME for the domain names so we're stuck with the ugly
domain names.
Only solution I can see to this is make some pages that redirect there
Hi,
I vote for redirect or just a link to it from our site, like we do for our
Markmail and Apache mailing lists archives.
Linking is no issue. The issue is how is a user going to remember or type if
needed those rather ugly domain names?
Justin
Exhibit A [1]. It was as simple as adding their embed script.
[1] http://people.apache.org/~mkessler/nabble.html
-Mark
On Mon, Aug 19, 2013 at 8:17 PM, Justin Mclean jus...@classsoftware.comwrote:
Hi,
I vote for redirect or just a link to it from our site, like we do for
our
Markmail
Hi,
Exhibit A [1]. It was as simple as adding their embed script.
[1] http://people.apache.org/~mkessler/nabble.html
Nice. It works but it does uses frames - we may not want to do that.
Justin
Your right I can see it there using 3 IFrames. But It seems to work in lots
of crazy places.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/User-forms-issues-tp57p66.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
, Number (or any other type) there a few if checks that fail as
it not checking for null but doing a straight if (data). I seem to recall a
few other JIRA issues around this.
3. Mustella DG test take ages to run.
Thanks,
Justin
as it not
checking for null but doing a straight if (data). I seem to recall a
few other JIRA issues around this.
For sure, which is why we never tried to fix the non-complex object
scenario. You are welcome to keep trying, but it might be best at this
point to revert and work locally. And one thought I
, but
there's at least one I can't find that's still causing an issue.
IMO, this is a corner case: most folks have complex data objects,
Yep agree, however there does seem to be serval other related issues it's
uncovered.
Yes they do, so I generally run a subfolder of tests.
I do
Hi,
There quite a few newly added unresolved issues in JIRA, any chance is some
help in getting them resolved?
https://issues.apache.org/jira/issues/?filter=12324692
As we've just released 4.10 it's a good time to show that we can be responsive
to users of the SDK issues and needs.
Thanks
hi
I have installed the rc4 sdk with the latest sdk installer. I noticed that,
by default, min. player version is marked as 11.8 in the flex-config.xml.
is it supposed to point 11.8 or its an error?
flex-config
!-- Specifies the minimum player version that will run the compiled
SWF. --
On Aug 2, 2013 2:24 AM, Jagan Langa Sami Durai jaga...@sybrant.com
wrote:
hi
I have installed the rc4 sdk with the latest sdk installer. I noticed
that,
by default, min. player version is marked as 11.8 in the flex-config.xml.
is it supposed to point 11.8 or its an error?
flex-config
If I recall correctly, it's version 10.1
EdB
On Fri, Aug 2, 2013 at 11:39 AM, Jagan Langa Sami Durai
jaga...@sybrant.com wrote:
Hi,
correct me if my understanding is wrong. Developer may prefer any latest
flash player while compiling and releasing. But my question is. what is the
minimum
Hi,
If I recall correctly, it's version 10.1
Close the minimum is 10.2. This is in the README.
The 4.10 SDK wont compile with 10.1 but it may be possible to get it working on
10.1 with a little work.
Thanks.
Justin
Hi,
Place all discussion about Apache Flex 4.10.0 RC 4 here. Any questions you
have, issues you run into etc etc
Thanks,
Justin
Hi,
Now RC4 is online, can you please point the Installer to it so people
have easy access?
Done.
Justin
It doesn't work the way it should anymore..
flash player is not chooseable and the installer does not automatically fill in
the sdk.
Regards,
SWEN VAN ZANTEN
Hoofdstraat 160
2171 BL, Sassenheim
Op 1 aug. 2013, om 12:46 heeft Justin Mclean jus...@classsoftware.com het
volgende geschreven:
Same here... typo?
EdB
On Thu, Aug 1, 2013 at 12:51 PM, Swen van Zanten f...@hdsign.nl wrote:
It doesn't work the way it should anymore..
flash player is not chooseable and the installer does not automatically fill
in the sdk.
Regards,
SWEN VAN ZANTEN
Hoofdstraat 160
2171 BL,
True, but there are no options for the choice of flashplayer, so the installer
cannot proceed
aYo
www.ayobinitie.com
mrbinitie.blogspot.com
From: Justin Mclean
Sent: Thursday, 1 August 2013 11:46
To: dev@flex.apache.org
Hi,
Now RC4 is online, can you please point the Installer
Ah, I see (some of) it:
file name=FlexVersions versions=4.10.0 RC4,4.9.1,Nightly
default=4.10.0 RC3 /
Need to change the 'default' attribute as well...
EdB
On Thu, Aug 1, 2013 at 12:51 PM, a...@binitie.com wrote:
True, but there are no options for the choice of flashplayer, so the
HI,
file name=FlexVersions versions=4.10.0 RC4,4.9.1,Nightly
default=4.10.0 RC3 /
Sorry about that - just fixing.
Justin
commits@ or issues@ I would say what is better but what is sure is it
pollutes the dev list.
Those 2 lists are followed as well by committers or at least PMCs, otherwise
what do you thing about another list builds@ ? does it worth ?
-Fred
-Message d'origine-
From: Alex Harui
Sent
I think commits@f.a.o would be the best place. Builds break because of bad
commits (most of the times)
Moreover an additional list (ex. builds@f.a.o) would be a bit of an
overkill.
Thanks,
Om
On Sat, Jun 29, 2013 at 12:16 AM, Frédéric THOMAS
webdoubl...@hotmail.comwrote:
commits@ or issues@ I
break because of bad
commits (most of the times)
Moreover an additional list (ex. builds@f.a.o) would be a bit of an
overkill.
Thanks,
Om
On Sat, Jun 29, 2013 at 12:16 AM, Frédéric THOMAS
webdoubl...@hotmail.comwrote:
commits@ or issues@ I would say what is better but what is sure
On Fri, Jun 28, 2013 at 12:55 AM, Justin Mclean jus...@classsoftware.comwrote:
Hi,
I was just wondering: would it be better if I have Jenkins send the
Mustella run emails to 'issues@'?
+0 from me. Someone may break the build and not be aware of it, but if
others think that's OK go ahead
it be better if I have Jenkins send the
Mustella run emails to 'issues@'?
+0 from me. Someone may break the build and not be aware of it, but if
others think that's OK go ahead, I guess someone could politely point it
out and suggest they subscribe to issues@ when it occurs.
Just to assuage
Hi,
I was just wondering: would it be better if I have Jenkins send the
Mustella run emails to 'issues@'?
The way it stands now, all three runs (main, AIR and mobile) have
tests failing (even after -failures). This means that per full run,
three emails will be sent... twice a day. That will put
Hi,
I was just wondering: would it be better if I have Jenkins send the
Mustella run emails to 'issues@'?
+0 from me. Someone may break the build and not be aware of it, but if others
think that's OK go ahead, I guess someone could politely point it out and
suggest they subscribe to issues
On 6/28/13 12:32 AM, Erik de Bruin e...@ixsoftware.nl wrote:
Hi,
I was just wondering: would it be better if I have Jenkins send the
Mustella run emails to 'issues@'?
Wouldn't commits@ be better?
The way it stands now, all three runs (main, AIR and mobile) have
tests failing (even after
HI,
I don't have access to, nor knowledge off, a Linux distro, but if you
have boring copy-paste stuff to fix for those path issues I'll be
glad to help...
Bit more involved than that. In some cases it just files names with wrong case
so it doesn't compile, in others it run time loaded assets
Hi,
Here's my rough notes from the other week.
Application 1 error - height different in one test
collections 0 errors
CompiletimeLocalization - fails to compile
components - fails to compile
containers - JPG path/case issues
[java
Hi,
And while it would be nice to get all the test to pass I think having them
compile and the obvious path issues fixed is probably good enough for an
initial release.
There still one or open build questions as well eg What do we do about the
Pixel Blender files?
Hopefully someone with more
directory,
/tmp/Adobe, is created which causes compilation conflicts and permission
issues.
--
Key: FLEX-14805
Hi,
When working through the release procedure I noticed some issues with
the ASDoc build:
1) the build complains there is a property 'tlf.branch' that is not
set; setting this property to '${basedir}/../flex-tlf/textLayout' in
'build.properties' seems to fix this. Shouldn't this be a default
Hi,
Tell me about it - mentioned it a few months ago.
Justin
On 5/21/13 3:41 AM, Erik de Bruin e...@ixsoftware.nl wrote:
Hi,
When working through the release procedure I noticed some issues with
the ASDoc build:
1) the build complains there is a property 'tlf.branch' that is not
set; setting this property to '${basedir}/../flex-tlf/textLayout
1) the build complains there is a property 'tlf.branch' that is not
set; setting this property to '${basedir}/../flex-tlf/textLayout' in
'build.properties' seems to fix this. Shouldn't this be a default
setting (the property is presently commented out)?
Actually, I wanted to get rid of
Here is the actual output for that issue:
[asdoc]
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/airspark/src/spark/components/WindowedApplication.as:
Error: Can not resolve a multiname reference unambiguously.
spark.components:Alert (from
I don't see this error during a normal build, only when I specifically
run 'ant asdoc'.
EdB
On Tue, May 21, 2013 at 7:27 PM, Erik de Bruin e...@ixsoftware.nl wrote:
Here is the actual output for that issue:
[asdoc]
Ok, now I see what the issue is. WindowedApplication is in the
spark.components package along with the experimental
spark.components.Alert, so an attempt to use mx.controls.Alert needs to be
fully qualified.
So, yes, changing to fully qualified is correct (or you can be brave,
remove the import
I love that 'or you can be brave'
On 21 May 2013 19:09, Alex Harui aha...@adobe.com wrote:
Ok, now I see what the issue is. WindowedApplication is in the
spark.components package along with the experimental
spark.components.Alert, so an attempt to use mx.controls.Alert needs to be
fully
Do we ever get feature requests that have a high criticality but people
don't implement it or don't agree with it? I mean what happens to the
issues. Do we just keep the in Jira for life or is there an action that
should be performed?
I was looking at an issue[1] and was thinking it sounded
and community.
I mean what happens to the
issues. Do we just keep the in Jira for life or is there an action that
should be performed?
IMO, keep it for life because you never know when a dozen folks will start
complaining about something. Voting should remain open in most cases.
I just bring
Hi,
It's marked as a feature request not a bug so I'd leave as major but no
objections if it was moved to minor.
Thanks,
Justin
Just FYI, Apache JIRA has a default priority of 'Major' when a new
issue/bug is created. It kind of makes sense because JIRA is being safe by
selecting the middle value from the list:
Blocker Critical Major Minor Trivial
It is easy to not pause and give the priority a thought when filing a
Was just curious since it was swept up in the search of Critical and major
issues :P
On Mon, May 6, 2013 at 8:18 PM, Justin Mclean jus...@classsoftware.comwrote:
Hi,
It's marked as a feature request not a bug so I'd leave as major but no
objections if it was moved to minor.
Thanks,
Justin
Hi,
Running the a test over the (with the new -advanced-telemetry option) shows
that GC is the biggest issue and I assume that because of the many temporary
objects created when doing string+= string? getClassInfo is next, followed by
the various global describeType/describeMetaData,
I like the idea of updating them to Won't fix and direct them to reach
out for the group to look back into them.
On Sat, Apr 20, 2013 at 10:57 PM, Alex Harui aha...@adobe.com wrote:
On 4/20/13 10:48 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
Rather than keeping them as
On Sat, Apr 20, 2013 at 11:22 PM, Alex Harui aha...@adobe.com wrote:
4. If someone cares enough to complain on the list, one of us can open for
them.
Agreed. I like 4. If they are an issue people will reraise.
--
Jonathan Campos
Hi Justin,
FYI, few years ago, I did a closer examination of existing limitations of
current DateFormatter from Flex3 and suggested a few fixes for the
following issues (old JIRA numeration):
Fixed SDK-23069 https://bugs.adobe.com/jira/browse/SDK-23069[Localization
Hi,
Thanks for that I take a look tomorrow.
I have to ask did you write all the code yourself and are able to donate it to
Apache Flex? From what I can see it's under a Apache style licence already.
https://github.com/JabbyPanda/DateField4/blob/master/LICENSE
Thanks,
Justin
On 4/19/13 5:28 PM, Justin Mclean jus...@classsoftware.com wrote:
Alex if you could review the tests as I'm not 100% familiar with Mustella I'd
appreciate it.
Looks like the right pattern for testing methods. Good job!
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
Anything but 3.
We should leave the MX component issues closed and reopen the spark and
some framework issues :p
But in two years from now well have to get around to them lol
-Mark
On Sat, Apr 20, 2013 at 7:58 PM, Justin Mclean jus...@classsoftware.comwrote:
Hi,
There's 4000+ issue
Personally, I would say #4 -- assuming people can vote on closed tickets or
re-open them if they run across them. There are quite a few duplicates
(not hundreds, but more than 30) of those old tickets, and having them
reopened I would imagine could cause issues.
-Nick
On Sat, Apr 20, 2013 at 8
someone brings up the issue again.
From a glance there are issues that do need to be looked at and there ate some
interesting enhancements and ideas.
For instance:
https://issues.apache.org/jira/browse/FLEX-32879
https://issues.apache.org/jira/browse/FLEX-32925
https://issues.apache.org/jira/browse
.
https://issues.apache.org/jira/issues/?filter=12321179
Would anyone object to reopening:
1. All the major and above bugs in this state? (about 200 issues)
2. All of the major and above issues? (about 600 issues)
3. Reopen everything!
4. Leave as they are.
As this could be done
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.?
Justin
301 - 400 of 446 matches
Mail list logo
