I’ve created an issue to ask the question: https://issues.apache.org/jira/browse/INFRA-9352 <https://issues.apache.org/jira/browse/INFRA-9352>
For the actual import we should probably wait until we’ve got the code in place as well. Cheers, Till > On Mar 28, 2015, at 3:58 PM, Till Westmann <[email protected]> wrote: > > Hi, > >> On Mar 27, 2015, at 8:55 PM, Mattmann, Chris A (3980) >> <[email protected] <mailto:[email protected]>> wrote: >> >> There is a Google Doc - can Till send a link around if anyone >> hasn’t done an ICLA yet? > > Here’s to doc: http://goo.gl/XAuNOZ <http://goo.gl/XAuNOZ> > But to save the trip to the doc: everybody on the list has filed the ICLA, > but Inci doesn’t have an account yet. > >> As for importing JIRA issues - it can be done - but is difficult >> depending on the JIRA versions etc. > > It seems that we don’t have to much variance regarding the JIRA version > (probably infra is only running 1 version). > But I’m wondering if anybody has experience mapping Goole Code issue fields > to JIRA fields ... > >> I would recommend to work with >> infra and then to please copy the list as steps are progressed. First >> step may be to create a ticket to do the import. > > Sounds good. Will do that. > > Cheers, > Till > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Chief Architect >> Instrument Software and Science Data Systems Section (398) >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 168-519, Mailstop: 168-527 >> Email: [email protected] <mailto:[email protected]> >> WWW: http://sunset.usc.edu/~mattmann/ <http://sunset.usc.edu/~mattmann/> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Associate Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> >> >> >> >> -----Original Message----- >> From: Henry Saputra <[email protected] >> <mailto:[email protected]>> >> Reply-To: "[email protected] >> <mailto:[email protected]>" >> <[email protected] >> <mailto:[email protected]>> >> Date: Thursday, March 26, 2015 at 4:43 PM >> To: "[email protected] >> <mailto:[email protected]>" >> <[email protected] >> <mailto:[email protected]>> >> Subject: Re: infra next steps? >> >>> Hmm never try it before. Maybe Google code could help if we send email to >>> them? >>> >>> Hopefully they have escape plan before shutting down. >>> >>> Till, have all initial committers signed the ICLA and got account? >>> >>> - Henry >>> >>> On Thu, Mar 26, 2015 at 4:01 PM, Till Westmann <[email protected] >>> <mailto:[email protected]>> wrote: >>>> We've got the mailing list, the JIRA project and now 2 git repos. >>>> We didn't ask for anything more so far. >>>> Is there something else that's usually needed? >>>> >>>> An interesting question could be, if there's a way to import existing >>>> bugs >>>> from the current issue trackers (AsterixDB and Hyracks) on Google Code. >>>> Do you know of if somebody has automated that process before? >>>> >>>> Thanks, >>>> Till >>>> >>>> >>>> On 26 Mar 2015, at 14:02, Ate Douma wrote: >>>> >>>>> Gavin just asked on https://issues.apache.org/jira/browse/INFRA-9306 >>>>> <https://issues.apache.org/jira/browse/INFRA-9306> if >>>>> there is anything else pending for infra to setup? >>>>> >>>>> I think the next step would be the initial code import, right? >>>>> For which the SGA first needs to be provided. >>>>> >>>>> If there is anything else to setup which infra can pick up, we should >>>>> create tickets for them. >>>>> >>>>> Ate >> >
