Re: [Poll] Old Flex closed and later issues
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 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 non-committers can't re-open. At least, in the Adobe days, we'd hear about closed bugs and have to open them for folks. So, I think the comment has to direct them to request a change in status on the users mailing list? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Poll] Old Flex closed and later issues
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
Re: [Poll] Old Flex closed and later issues
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 in the closed and later state of these about 3000 are marked as bugs and about 200 have a priority of major or more. 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 with a batch operation no JIRA emails would be sent out. Thanks, Justin
Re: [Poll] Old Flex closed and later issues
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:16 PM, Mark Kessler kesslerconsult...@gmail.comwrote: 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.com wrote: Hi, There's 4000+ issue in the closed and later state of these about 3000 are marked as bugs and about 200 have a priority of major or more. 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 with a batch operation no JIRA emails would be sent out. Thanks, Justin
Re: [Poll] Old Flex closed and later issues
Hi, Personally, I would say #4 -- assuming people can vote on closed tickets or re-open them if they run across them. I not sure an ordinary user can reopen or vote on them. My issue is that having them marked Later implies we'll get around to them at sometime when in fact we wont unless 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/FLEX-32825 https://issues.apache.org/jira/browse/FLEX-32210 Sure there's many many more. Justin
Re: [Poll] Old Flex closed and later issues
4. If someone cares enough to complain on the list, one of us can open for them. On 4/20/13 4:58 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, There's 4000+ issue in the closed and later state of these about 3000 are marked as bugs and about 200 have a priority of major or more. 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 with a batch operation no JIRA emails would be sent out. Thanks, Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Poll] Old Flex closed and later issues
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
Re: [Poll] Old Flex closed and later issues
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 non-committers can't re-open. At least, in the Adobe days, we'd hear about closed bugs and have to open them for folks. So, I think the comment has to direct them to request a change in status on the users mailing list? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
