Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B0C4E10F0D for ; Mon, 8 Jul 2013 17:10:23 +0000 (UTC) Received: (qmail 60300 invoked by uid 500); 8 Jul 2013 17:10:23 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 60232 invoked by uid 500); 8 Jul 2013 17:10:21 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 60218 invoked by uid 99); 8 Jul 2013 17:10:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Jul 2013 17:10:20 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Jul 2013 17:10:16 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=rTfmXgd8Tss6CIpa9aGcnVQI2Qn1LLsTwrthXRutAIo=; b=eoMK+h1atFFYYoyCVoSJ9+129yKXpa1qocCpbXgvaSlEH8PRErmyzfjZ/KtmKEdbv0teMQ9xAUBH47LmweERGJrPUSGlE+8wyyoEvOYkabMKC6onAU5FfcRS9+j+f3j38eElj8kj7ng0/O2V3g8RBEw95Ty/mwhiaIWfPLuDWEE=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-3.v29.ch3.sourceforge.com) by sfs-alluradaemon-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UwEwm-0004oX-4e for allura-dev@incubator.apache.org; Mon, 08 Jul 2013 17:09:56 +0000 Content-Type: multipart/related; boundary="===============3711806517502240267==" MIME-Version: 1.0 To: "[allura:tickets] " <4213@tickets.allura.p.re.sf.net> From: "Tim Van Steenburgh" Reply-To: "[allura:tickets] " <4213@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #4213 Import from trac into ticket tool Message-ID:

Date: Mon, 08 Jul 2013 17:09:56 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============3711806517502240267== Content-Type: multipart/alternative; boundary="===============2145266423156305373==" MIME-Version: 1.0 --===============2145266423156305373== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit See [#6441] for follow-up work. --- ** [tickets:#4213] Import from trac into ticket tool** **Status:** closed **Labels:** import 42cc **Created:** Thu May 17, 2012 02:44 PM UTC by Dave Brondsema **Last Updated:** Mon Jul 08, 2013 05:07 PM UTC **Owner:** nobody A script exists at `scripts/trac_export.py` to extract trac tickets, and can be imported with `scripts/allura_import.py` Jon Schewe describes the whole process at Improvements needed: * stability / handle errors (and possibly some refactor/cleanup) * fetch and upload attachments (add uploads to import API?) * set up milestones and proper field types (add to API? or setup directly, first?) * SourceForge: a ScriptTask for us to run it for projects, including the user mapping See [#6139] for wiki import. We should strongly consider making our ticket import format match our API format, so that a backup [#3154] can be restored directly. ... or do that later --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============2145266423156305373== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

See [#6441] for follow-up work.

[tickets:#4213] Import from trac into ticket tool

Status: closed
Labels: import 42cc
Created: Thu May 17, 2012 02:44 PM UTC by Dave Brondsema
Last Updated: Mon Jul 08, 2013 05:07 PM UTC
Owner: nobody

A script exists at scripts/trac_export.py to extract trac tickets, and can be imported with scripts/allura_import.py Jon Schewe describes the whole process at http://mail-archives.apache.org/mod_mbox/incubator-allura-users/201303.mbox/%3CCALpcnoxEG%3DNJ7UG1dfOKj%2BbEPMtybGNStXZPVjfHrLyLDz%3DXLA%40mail.gmail.com%3E

Improvements needed:

  • stability / handle errors (and possibly some refactor/cleanup)
  • fetch and upload attachments (add uploads to import API?)
  • set up milestones and proper field types (add to API? or setup directly, first?)
  • SourceForge: a ScriptTask for us to run it for projects, including the user mapping

See [#6139] for wiki import.

We should strongly consider making our ticket import format match our API format, so that a backup [#3154] can be restored directly. ... or do that later

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============2145266423156305373==-- --===============3711806517502240267==--