Alex, I think that going forward as you stated would be ok. At this point I think it's most important to know what the bugs are (and get issue numbers assigned so we can manage them), then to worry about the neuances of some of the history from the old repository.
I do think the version numbers and steps to reproduce are extremely important however. If the steps-to-reproduce end up as a comment, I think that is acceptable (I just don't want to loose the content), but the version number is something very important to filter on, esp. if we will eventually be working with multiple versions in our trunk. -Nick On Fri, Jan 13, 2012 at 3:12 PM, Alex Harui <aha...@adobe.com> wrote: > We’re still waiting for JIRA to get set up (and yes, we are still waiting > for legal to clear the source code). But in investigating what it will > take to transfer the current JIRA issues to Apache, I found this article > [1]. > It talks about username conflicts as being a major pain. To try to reduce > pain and expedite the JIRA transfer, I am seriously considering changing > the authors of all current issues to something like “AdobeFlexSDK”. If I > can, I will take the original author and add it to the comments or a custom > field or something like that. I’m also looking for a field to store the > original Adobe issue number as well. Doing so might then invalidate the > way comments are managed, so I might also take all current comments and > concatenate them into one long comment submitted by AdobeFlexSDK as well. > Similarly, the person who submitted attachments may also become > AdobeFlexSDK with no reference to who submitted it. > > Also, Flex JIRA issues have lots of custom fields that I expect Apache > JIRA won’t have. I don’t know if we’ll be able to get the same fields and > we probably don’t really need most of them. Let me know if you feel like > there is some field other than the obvious (steps to reproduce, date, > version) that needs to be preserved. > > [1] https://cwiki.apache.org/INFRA/merging-jiras.html > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui >
