https://issues.apache.org/jira-test/browse/WAVE
On Apr 27, 2011, at 2:31 PM, Yuri Z wrote: > The link is missing. > > 2011/4/28 Michael MacFadden <[email protected]> > >> All, >> >> The Infra guys have done a dry run of the Jira import. The results can be >> seen here: >> >> It's not perfect, but I think that any issues that need tweaking can be >> done in a manual way. Unless there are major objections we are going to >> finalize the import tomorrow evening. At which point we will be live on >> Jira. Please let me know before then if there are any problems you think we >> can address after the import. Thanks. >> >> ~Michael >> >> On Apr 26, 2011, at 7:03 PM, David Hearnden wrote: >> >>> +1 >>> (most of Australia has just come back from a 5-day weekend, so we've been >>> pretty quiet). >>> >>> Thanks Michael, >>> >>> -Dave >>> >>> On Tue, Apr 26, 2011 at 4:20 AM, Michael MacFadden < >>> [email protected]> wrote: >>> >>>> I have created the INFRA Jira issue here: >>>> >>>> https://issues.apache.org/jira/browse/INFRA-3596 >>>> >>>> I will keep you all posted. >>>> >>>> ~Michael >>>> >>>> >>>> On Apr 24, 2011, at 10:03 PM, Yuri Z. wrote: >>>> >>>>> +1 >>>>> >>>>> Sent from my iPhone >>>>> >>>>> On 25 באפר 2011, at 06:18, James Purser <[email protected]> >> wrote: >>>>> >>>>>> +1 >>>>>> >>>>>> On Mon, Apr 25, 2011 at 1:13 PM, Michael MacFadden < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> All, >>>>>>> >>>>>>> Unless I get any objection. Let's "freeze" the Google Code Issue >>>>>>> repository. To my knowledge there is no way to actually turn off the >>>>>>> repository. The only thing I think we can do is change the "User" >>>> Template >>>>>>> for the bug to contain a message saying this system is deprecated and >>>> offer >>>>>>> a link to the new Jira system. >>>>>>> >>>>>>> Beyond that I will take an export of Google Code tonight and submit >> an >>>>>>> INFRA Jira issue for the CSV for import tomorrow. Thanks. >>>>>>> >>>>>>> ~Michael >>>>>>> >>>>>>> >>>>>>> On Apr 24, 2011, at 8:37 AM, Yuri Z wrote: >>>>>>> >>>>>>>> The sooner the better imho. >>>>>>>> >>>>>>>> 2011/4/24 Michael MacFadden <[email protected]> >>>>>>>> >>>>>>>>> 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] >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> James Purser >>>>>> Collaborynth >>>>>> http://collaborynth.com.au >>>>>> Mob: +61 406 576 553 >>>>>> Wave: [email protected] >>>> >>>> >> >>
