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 longer existed. So I handled the issue (tested, closed out), which seemed reasonable. 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? I mean we put those labels on there like honey-pots lol. [1] https://issues.apache.org/jira/browse/FLEX-26157 [2] https://issues.apache.org/jira/browse/FLEX-28064 -Mark On Sat, Apr 20, 2013 at 6:26 PM, Alex Harui <aha...@adobe.com> wrote: > > > > On 4/20/13 2:48 PM, "Mark Kessler" <kesslerconsult...@gmail.com> 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 where they confirm it still exists, do we just leave > it > > until a fix is suggested or a patch is submitted? > > > IMO, you are welcome to fix as many of these as you have time and > inclination. Of course, if you want to pick up a harder bug to challenge > your bug fixing skills I will try to answer questions if they arise. > > > Don't want to preemptively solve issues if they are there to entice > people > > to contribute. > > > > > > -Mark > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
