Hi Alex, Just an idea. Why not open everything up for JIRA submissions/patches after the initial JIRA release? JIRA bugs imported after that can always be marked as duplicates and/or linked to any newer entered JIRA issues as required.
Not being able to submit patches until end of February may mean people start to loose interest in doing so and creates a barrier for Flex developers at large being involved (in my opinion). I assume there's no way that this process can be speeded up with community help (happy to help if I can) or perhaps by releasing the JIRA issues in smaller batches? Don't take this the wrong way I know you've been working hard at this and I can't imagine how much work it's been to get the project to this stage, it just as a Flex developer I'm a little impatient in wanting to contribute to the project. Another idea. Is there any way the whiteboard area can be opened up to people other than the current list of committers? Thanks, Justin On 23/01/2012, at 4:43 PM, Alex Harui wrote: > I'm shooting for SDK bugs this week. There is a lot of legal issues with > the rest of the drop and it might be end of February, especially with me > being out for a couple of weeks. > > > On 1/22/12 9:33 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > >> Hi Alex, >> >>> I would prefer if you would wait until we get all the code in and the JIRA >>> bugs migrated. >> >> OK I'll hold off until then. I know you're working hard at this and it taken >> a >> little longer than expected because of the legal issues and the complexities >> involved. >> >> Can I ask what's your estimate to when we have the code drop and JIRA >> migrated. I think you mentioned something about going to China for a couple >> of >> weeks soon is this likely to delay the initial drop/JIRA migration? >> >> Thanks, >> Justin > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui >
