When do we want to schedule the cut over? I can put the request in today...
~Michael On Apr 23, 2011, at 2:44 PM, James Purser wrote: > +1 To the issue freeze and migrate option > > On Sun, Apr 24, 2011 at 4:54 AM, Michael MacFadden < > [email protected]> wrote: > >> I think everything is going to make it over, with the exception of >> attachments. But that doesn't seem to be much of an issue (no pun intended). >> >> ~Michael >> >> >> On Apr 23, 2011, at 11:45 AM, Arlen Beiler <[email protected]> wrote: >> >>> Issue freeze would be a good idea. Is there anything that cannot be >>> migrated? >>> >>> On Sat, Apr 23, 2011 at 1:49 PM, Michael MacFadden < >>> [email protected]> wrote: >>> >>>> All, >>>> >>>> I would like to recommend we cut over from Google Code to Jira with in >> the >>>> next few days. Once the CSV export is satisfactory, I simply need to >> place >>>> the file on people.apache.org and reference that in a new Jira Issue in >>>> the INFRA project requesting the import. >>>> >>>> After we do the import, all activity should essentially stop in the >> Google >>>> Code Issue manager and we should make all new issues and changes to >> issues >>>> in Jira. When do we want to target the cut over? We should probably >> have a >>>> mini "issue freeze" for a day or so while we do the migration. What do >>>> people think? >>>> >>>> >>>> ~Michael >> > > > > -- > James Purser > Collaborynth > http://collaborynth.com.au > Mob: +61 406 576 553 > Wave: [email protected]
