Reporting bugs against ASC 2.0 is currently less than ideal. Customers use bugbase.adobe.com but have to report the bug against the AIR ASK, noting that it is a compiler bug. Specifically, they should set "Product: Adobe AIR", "Version: 3.x", "Product Area: AIR SDK" and include a the note in the report that the bug is in ASC 2. Ugh.
- Gordon -----Original Message----- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, January 16, 2013 11:35 AM To: dev@flex.apache.org Subject: Re: ASC 2.0 bugbase On 1/16/13 11:24 AM, "Michael A. Labriola" <labri...@digitalprimates.net> wrote: >> But the logistical question is: Should we automatically bring over >> every change for every bug? Or just selected bugs? >> I would strongly prefer that we don't automatically copy the ASC 2.0 >> bug base over to Apache Flex, especially by scraping. > > Just to clarify, I didn't suggest that. I suggested we scrape the > pages automatically into something like a google doc, which could be > periodically reviewed by members here. Then we could manually enter > the relevant bugs. Not suggesting this is perfect either, but it was > my best suggestion at the moment. OK, sorry I mis-understood. @Gordon, is ASC using bugbase.adobe.com or do these bugs eventually get transferred to another bugbase we can get reports from? -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
