Arvind, Sounds like a plan, thanks for helping with this. Would be possible, as part of the scrubbing, that all those JIRAs in the subject have YOOZIE-# (similar to what Roman did for the GitHub issues adding GH-#)?
Thanks. Alejandro On Thu, Sep 8, 2011 at 10:16 AM, Arvind Prabhakar <[email protected]> wrote: > Mohammad, Roman, > > Roman and I just chatted about this and he agrees that I should help > out in creating a JIRA dump from the raw data files that have been > attached to INFRA-3883. It will take me close to a day or so to > rebuild everything and do the export, so I expect it to be done by mid > day tomorrow or so. > > Once I get the XML dump I will be happy to hand it off to you for > further processing. The things that will need to be worked out are the > following: > > 1. Scrub out personal details such as email addresses and names for > users who do not explicitly grant consent. > 2. Modify the dump so that the issues do not conflict with existing > issues. For example OOZIE-1 will conflict with the one in ASF JIRA. > > Please let me know if this plan sounds reasonable to you. > > Thanks, > Arvind > > On Thu, Sep 8, 2011 at 8:50 AM, Roman Shaposhnik <[email protected]> wrote: >> On Thu, Sep 8, 2011 at 12:54 AM, Mohammad Islam <[email protected]> wrote: >>> I already created a INFRA JIRA >>> (https://issues.apache.org/jira/browse/INFRA-3883) to track this. >>> In that JIRA, I uploaded the mysql data file. You guys could use the file >>> for this. >> >> I see. Well, there's bad news and good news. Bad news: this is not a >> dump, hence the >> quality of the import will be about as high as the quality of the GH >> import (IOW, we will >> lose fields). Good news: not a lot of data, so should be doable. >> Question: what exact >> version of JIRA generated this data? >> >> Thanks, >> Roman. >> >> P.S. Oh, and it is really annoying that I'm not part of the Apache >> Oozie JIRA. Certain >> feature are simply turned off for me. >> >
