Hi, We're scheduling the Jira migration for Maven projects on the week-end of 4/5/6 april. If this schedule is fine for Groovy, I suppose it would be ok to add Groovy Jira project to the actual list [1] Just tell, and I'll avoid to remove Groovy from the full dump we'll have during the migration.
Regards, Hervé Notice: please CC me if necessary, since I'm not subscribed to general@incubator [1] https://issues.apache.org/jira/browse/INFRA-9116 Le lundi 16 mars 2015 09:53:00 Stephen Connolly a écrit : > Arg! hit send too soon. > > You should really check in with Hervé to confirm that Groovy was in the > export. I am 99% confident that your issues and comments are in the XML > dump, but you really should check with Hervé to be certain. > > Also you may want to ask Mark Thomas what exactly is involved in preparing > and doing such an import. Our own timelines for Maven's switch may not > align with the Groovy incubation timelines... (mind you we are all at the > grace of Ben for getting our timeline for the second export he committed to > the Maven project) > > On 16 March 2015 at 09:49, Stephen Connolly <stephen.alan.conno...@gmail.com > > wrote: > > > > > > > > On 16 March 2015 at 09:19, Cédric Champeau <cedric.champ...@gmail.com> > > > > wrote: > >> Thanks Stephen, sounds like a good news. For us the attachments do not > >> matter much, there are not so many. However, keeping track of comments is > >> very important, because some issues have a lot of discussions. > >> > >> 2015-03-16 10:08 GMT+01:00 Stephen Connolly < > >> stephen.alan.conno...@gmail.com > >> > >> > On 16 March 2015 at 08:55, Jochen Theodorou <blackd...@gmx.org> wrote: > >> > > Am 16.03.2015 09:25, schrieb Upayavira: > >> > >> When Stephen Connolly says ”We @ Maven will have a full dump of the > >> > >> Codehaus JIRA and we have a VM set > >> > >> up to test migration…” isn’t he implying that the Groovy issues are > >> > >> *included* in that? I.e. there’s not so much for you to worry about > >> > >> here? > >> > > > >> > > Even if Stephen gets a full dump, this does not mean we will get the > >> > > Groovy part out of it. Ben was so far telling us he cannot give it > >> > > out > >> > > >> > like > >> > > >> > > that, because of private and internal data in there. Instead he > >> > > >> > suggested a > >> > > >> > > json export (which most likely will not contain everything) > >> > > >> > Well we are getting the full XML dump because that's all you can get > >> > via > >> > the XML dump, but whether we get *all* attachments or only those for > >> > >> Maven > >> > >> > is a different question. > >> > > >> > > So unless Stephy has this clear with his employee I stand on the > >> > > part, > >> > > that we don't have that. > >> > > >> > Clarification: Ben and I are co-workers. > >> > > >> > > bye Jochen > >> > > > >> > > -- > >> > > Jochen "blackdrag" Theodorou - Groovy Project Tech Lead > >> > > blog: http://blackdragsview.blogspot.com/ > >> > > german groovy discussion newsgroup: de.comp.lang.misc > >> > > For Groovy programming sources visit http://groovy-lang.org > >> > > > >> > > > >> > > --------------------------------------------------------------------- > >> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> > > For additional commands, e-mail: general-h...@incubator.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
