JIRA has a csv import feature. It has some quirks. I don't remember all of them. I've used it to import 1000's of issues from the IBM rational issue tracker. It wasn't fun and required several stages (mapping named values to JIRA ids, etc...).
-Tad On Mon, Jan 3, 2011 at 11:18 PM, Alex North <ano...@google.com> wrote: > Michael, could we informally nominate you as point on the project site? > > Meanwhile I assume JIRA has an API - does anyone have experience with it? > The Google project hosting issue tracker we currently use has a GData API > we > can use to pull the data. > > Alex > > On 4 January 2011 17:12, Michael MacFadden <michael.macfad...@gmail.com > >wrote: > > > I agree with Alex. We should get the project infrastructure for the > > project up and running before we move the code over. I am very > interested > > in getting the project site up and running and am more than willing to > help > > with Jira also. > > > > ~Michael > > > > On Jan 3, 2011, at 9:49 PM, Alex North wrote: > > > > > I've though a little about this, and I know Michael MacFadden has too. > My > > > first thoughts are that the code should move last, that being the most > > > crucial piece to keep working to support existing development. But > there > > are > > > a couple of other pieces to move to Apache infrastructure too. > > > > > > - Issues to JIRA > > > - Continuous build to Apache-hosted Hudson > > > - Documentation, etc (probably) > > > > > > I suggest we can move these first without interrupting development too > > much, > > > then move the code when everything else is in place. Thoughts? > > > > > > When it comes to moving the code, I'm not sure there is an easy way to > > > import mercurial history. If there's an existing tool, let's use it, > but > > > otherwise let's just take a snapshot at head and get on with life. > > There's > > > no complex branching or tags in our repositories, though we do have two > > > repositories to somehow squeeze into one (WIAB and the Splash > lightweight > > > client). > > > > > > On 3 January 2011 06:08, Andrus Adamchik <and...@objectstyle.org> > wrote: > > > > > >> infrastructure-...@a.o ( http://www.apache.org/dev/infra-mail.html ) > > >> > > >> But keep in mind that this has been discussed to death throughout > > Apache, > > >> and there is in fact an effort underway to provide git as an option > for > > the > > >> 'canonical' repo. For now it can be used on the client via git-svn. > > >> > > >> Andrus > > >> > > >> On Jan 2, 2011, at 8:47 PM, Zachary Jones wrote: > > >> > > >>> Where is the best place to have the OT disxussion about reasons for > > >>> SVN vs. Git? I've found Git quite intuitive from simple to complex, > > >>> and I'm curious how others in projects like ASF related with the 'new > > >>> tech' > > >>> > > >>> > > >>> Zak > > >>> > > >>> On Saturday, January 1, 2011, Andrus Adamchik < > and...@objectstyle.org> > > >> wrote: > > >>>> Now that we have almost all accounts in place, I think it is a good > > time > > >> to discuss migrating the Wave code to the ASF SVN. Not sure if there > is > > a > > >> way to import history/tags/branches from Mercurial to SVN? If not, I > > guess > > >> we'd have to just import the heads of all relevant branches. Anyways, > > that's > > >> a question for the Wave developers to answer - how do you want to > > proceed > > >> with this? > > >>>> > > >>>> Andrus > > >>> > > >> > > >> > > > > >
