On 4/20/13 4:30 PM, "Justin Mclean" wrote:
> Hi,
>
>> For me, if someone started complaining that one of the easy fix bugs was
>> affecting their productivity with Flex, but they didn't have the skills or
>> time to fix it, and nobody else jumped in, then I'd go and fix it for them.
>
> You
Hi,
> But honestly whats 3339 open issues among friends :p
At the currently rate of fixing about 2 years :-)
And there's these one's:
https://issues.apache.org/jira/issues/?filter=12321179
There's 4375 in this state. They were issues Adobe put off doing until a later
version of the SDK that w
Hi,
> For me, if someone started complaining that one of the easy fix bugs was
> affecting their productivity with Flex, but they didn't have the skills or
> time to fix it, and nobody else jumped in, then I'd go and fix it for them.
You mean like this one:
https://issues.apache.org/jira/browse/
Hi,
> But the [2] second one he confirmed it's still a bug and that's where my
> question came in.
> Should I just leave it until it a fix, suggested fix is posted on it?
Up to you if you have the time and skill and inclination to fix it go right
ahead, if not the bug is now in a state where so
Thanks guy,
But honestly whats 3339 open issues among friends :p
You know if we closed some of those resolved(that are marked open), our
closed percentage would be almost 90%.
-Mark
Hi,
> On confirmations by someone that an issue longer produces the bug,
> confirming and closing out the ticket makes sense.
Nope don't close until it actually fix or it's not an issue in some other way.
> But on ones where they confirm it still exists, do we just leave it
> until a fix is sugg
On 4/20/13 3:43 PM, "Mark Kessler" wrote:
> Should I
> just leave it until it a fix, suggested fix is posted on it?
IMO, you are under no obligation to fix any bug. But I'm really glad to see
your activity level so far.
For me, if someone started complaining that one of the easy fix bugs was
I'm just searching for keywords or components I'm still working on and
working on those issues out of convenience. Not really by the labels,
which explains the randomness of what I'm working on.
But my questions where based on 2 example issues. The first issue [1]
Jeremy confirmed the bug no long
On 4/20/13 2:48 PM, "Mark Kessler" wrote:
> I know the point of the easyfix / easytest labels to to allow new people a
> good starting point to help out. On confirmations by someone that an issue
> longer produces the bug, confirming and closing out the ticket makes
> sense. But on ones wher
I know the point of the easyfix / easytest labels to to allow new people a
good starting point to help out. On confirmations by someone that an issue
longer produces the bug, confirming and closing out the ticket makes
sense. But on ones where they confirm it still exists, do we just leave it
unt
10 matches
Mail list logo
