This works for me. Marko.
http://markorodriguez.com On Mar 17, 2015, at 2:47 PM, Stephen Mallette <[email protected]> wrote: > This weekend sounds good to me. Marko, could you throw in a +1 if you > agree? +1s or -1s from others are also welcome. > > As an aside to quality checks, I'm fine with you doing the "read-only > permission" approach if you think that is best. > > On Tue, Mar 17, 2015 at 4:42 PM, Mark Thomas <[email protected]> wrote: > >> On 16/03/2015 14:32, Stephen Mallette wrote: >>> Hi Mark, I think at this point we're ready for you to pull the trigger >>> on the migration to Jira. A handful of individuals responded to me with >>> github username to apache jira account email mappings. I can send those >>> to you directly when you are ready to move forward. A couple of >> questions: >>> >>> 1. Do you have a day when you will execute the migration? I presume we >>> will freeze GitHub issues as of that day and keep things frozen until >>> everything looks happy in Jira. >> >> How about this weekend? Freeze github from 20.00 UTC Saturday evening. I >> should have it all imported into Jira within a few hours but lets say >> within 24 hours to give me plenty of margin should things go wrong. >> >>> 2. Will we have a final chance to validate that our accounts, issues, >>> etc. look right in the "test" jira before you make the final migration >>> to the "production" jira? >> >> We could, but that is going to slow things down. The problem is that the >> import locks all other users out of Jira for a period of time. The best >> time to do that is unlikely to be the best time for the Tinkerpop >> community to review the test import. >> >> I'd rather configure the imported data with a read-only permission >> schema that I can switch to read/write once you confirm that it looks >> OK. Unless there are major issues, I'd rather fix any issues >> post-migration directly in the production instance. >> >>> Please let us know if there is anything else we need to consider in >>> moving forward with this. >> >> I need to give folks 72 hours notice for the Jira downtime so I need to >> know ASAP if this weekend works for you. >> >> Cheers, >> >> Mark >> >>
