Return-Path: X-Original-To: apmail-subversion-dev-archive@minotaur.apache.org Delivered-To: apmail-subversion-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 D07B8172B7 for ; Tue, 15 Sep 2015 18:02:33 +0000 (UTC) Received: (qmail 45161 invoked by uid 500); 15 Sep 2015 18:02:27 -0000 Delivered-To: apmail-subversion-dev-archive@subversion.apache.org Received: (qmail 45114 invoked by uid 500); 15 Sep 2015 18:02:27 -0000 Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@subversion.apache.org Received: (qmail 45104 invoked by uid 99); 15 Sep 2015 18:02:26 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2015 18:02:26 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 533B3C047F for ; Tue, 15 Sep 2015 18:02:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id B4BiKN3yPSSG for ; Tue, 15 Sep 2015 18:02:16 +0000 (UTC) Received: from mail-vk0-f47.google.com (mail-vk0-f47.google.com [209.85.213.47]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id E7578203A0 for ; Tue, 15 Sep 2015 18:02:15 +0000 (UTC) Received: by vkfp126 with SMTP id p126so85015863vkf.3 for ; Tue, 15 Sep 2015 11:02:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yx9qzJGbLrzEzjKRDlB9KZ2OFpuoQwHblRMJe9uosgg=; b=rnut5EeXLHHaRNV829brKTAW4Vd1/HJqy7268wFNF41vVvqI4bAaMy4pCJlM6U6bDw /asJ6s3xyy3IQPKpjZyBj+nsAAPsFwoPC24tNuZJOfQky3vzZYDEosmiYGBK6EdtWqJu 4+teKy57lT2NhoF9WWoGRWAUmeQ5U+Z4N36yWUJOZnaJalFoCqyfX8kFSi/5Vo7g7QiX w4asTuk9RWTgTLr28j5qVPgg/BX2TSbeKz/GEc4TRoo5QbfVoWu6TX+5paOesMcGnNkj NGrSW1rDP/b9jTCLtvxKa0tyvQ6Eprxt0CGAF87lg1+HpV3I5clIFI8LXSvvU9fqotr/ osjg== MIME-Version: 1.0 X-Received: by 10.31.140.143 with SMTP id o137mr19508801vkd.56.1442340128693; Tue, 15 Sep 2015 11:02:08 -0700 (PDT) Received: by 10.31.180.134 with HTTP; Tue, 15 Sep 2015 11:02:08 -0700 (PDT) In-Reply-To: References: <001201d0ef9d$31ef3a90$95cdafb0$@qqmail.nl> Date: Tue, 15 Sep 2015 13:02:08 -0500 Message-ID: Subject: Re: Migrating Subversion issues to ... From: Greg Stein To: Ivan Zhakov Cc: Subversion Development Content-Type: multipart/alternative; boundary=001a11425f98042521051fccfbf9 --001a11425f98042521051fccfbf9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable You can do it. File an INFRA ticket for porting our issues into JIRA, and note that you have some content for a test load. They do test loads often for incoming, so they have a runbook for that. (and post the INFRA ticket here, so others can Watch the ticket if they like) Cheers, -g On Tue, Sep 15, 2015 at 9:51 AM, Ivan Zhakov wrote: > On 15 September 2015 at 14:40, Mark Phippard wrote: > > On Tue, Sep 15, 2015 at 5:59 AM, Bert Huijben wrote: > >> > >> Hi All, > >> > >> > >> > >> Here at the hackathon in Berlin we are discussing issue trackers, and > more > >> particular how we should eventually move our issues to ASF > infrastructure. > >> An old TODO. > >> > >> > >> > >> Ivan just converted the data of the much smaller Serf issuetracker to > Jira > >> for the Apache Serf project, and he offers to perform the migration fo= r > >> Subversion too. > >> > >> > >> > >> > >> > >> I think we really have 3 options: > >> > >> [ ] Keep our issues on Tigris > >> > >> [ ] Migrate our issues to a new Bugzilla instance hosted by ASF infra > >> > >> [ ] Migrate to the standard ASF Jira installation > >> > >> > >> > >> In Jira we can keep our existing issuenumbers, while for Bugzilla we > would > >> need a separate instance. > >> > >> > >> > >> Personally I would choose the third option if we aim to keep as much > >> history as possible (including ascii art and attachments) available > after > >> the migration. The information in our issue database is just too > valuable to > >> lose=E2=80=A6. Even if it will take a few more years to get there. > >> > >> > >> > >> Bert > > > > > > +1 on migration. > > > > I would bias the decision in favor of doing the migration over trying t= o > > solve every problem and letting another year go by. > > > > If Ivan has a working migration for Jira then +1 for that. > > > > I think it is a mistake to get hung up on these other issues that are > > trivial in my opinion. Monospace vs proportional -- I do not believe > anyone > > really cares. Just let the ascii art get messed up. Old links not > working > > ... not a problem you can solve. Just move on. > > > > I would just migrate the data to Jira, not try to solve all these > problems > > and move forward. I have seen zero evidence in the years I have been > > involved in this project that anyone really cares about the issue > tracker. > > We go out of our way to actively discourage people from using it. To b= og > > down on migration over relatively small problems would just be a waste = of > > time and effort. It sounds like you already will be accomplishing a lo= t > by > > keeping issue numbers roughly the same. > > > > Take that victory and get this done. > > > It seems people generally support idea to move to ASF JIRA. I already > have some data converted and want to perform *test* import to ASF > JIRA. Just to see how it will like. Should I request ASF INFRA team do > this for us or such request supposed to be created by PMC chair? > > -- > Ivan Zhakov > --001a11425f98042521051fccfbf9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You can do it. File an INFRA ticket for porting our issues= into JIRA, and note that you have some content for a test load. They do te= st loads often for incoming, so they have a runbook for that.

(and post the INFRA ticket here, so others can Watch the ticket if th= ey like)

Cheers,
-g


On Tue,= Sep 15, 2015 at 9:51 AM, Ivan Zhakov <ivan@visualsvn.com> = wrote:
On 15 September 2015 at 14:40, Mark Phippard <markphip@gmail.com> wrote:
> On Tue, Sep 15, 2015 at 5:59 AM, Bert Huijben <bert@qqmail.nl> wrote:
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Hi Al= l,
>>
>>
>>
>> Here at the hackathon in Berlin we are discussing issue trackers, = and more
>> particular how we should eventually move our issues to ASF infrast= ructure.
>> An old TODO.
>>
>>
>>
>> Ivan just converted the data of the much smaller Serf issuetracker= to Jira
>> for the Apache Serf project, and he offers to perform the migratio= n for
>> Subversion too.
>>
>>
>>
>>
>>
>> I think we really have 3 options:
>>
>> [ ] Keep our issues on Tigris
>>
>> [ ] Migrate our issues to a new Bugzilla instance hosted by ASF in= fra
>>
>> [ ] Migrate to the standard ASF Jira installation
>>
>>
>>
>> In Jira we can keep our existing issuenumbers, while for Bugzilla = we would
>> need a separate instance.
>>
>>
>>
>> Personally I would choose the third option if we aim to keep as mu= ch
>> history as possible (including ascii art and attachments) availabl= e after
>> the migration. The information in our issue database is just too v= aluable to
>> lose=E2=80=A6. Even if it will take a few more years to get there.=
>>
>>
>>
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Bert<= br> >
>
> +1 on migration.
>
> I would bias the decision in favor of doing the migration over trying = to
> solve every problem and letting another year go by.
>
> If Ivan has a working migration for Jira then +1 for that.
>
> I think it is a mistake to get hung up on these other issues that are<= br> > trivial in my opinion.=C2=A0 Monospace vs proportional -- I do not bel= ieve anyone
> really cares.=C2=A0 Just let the ascii art get messed up.=C2=A0 Old li= nks not working
> ... not a problem you can solve.=C2=A0 Just move on.
>
> I would just migrate the data to Jira, not try to solve all these prob= lems
> and move forward.=C2=A0 I have seen zero evidence in the years I have = been
> involved in this project that anyone really cares about the issue trac= ker.
> We go out of our way to actively discourage people from using it.=C2= =A0 To bog
> down on migration over relatively small problems would just be a waste= of
> time and effort.=C2=A0 It sounds like you already will be accomplishin= g a lot by
> keeping issue numbers roughly the same.
>
> Take that victory and get this done.
>
It seems people generally support idea to move to ASF JIRA. I a= lready
have some data converted and want to perform *test* import=C2=A0 to ASF
JIRA. Just to see how it will like. Should I request ASF INFRA team do
this for us or such request supposed to be created by PMC chair?

--
Ivan Zhakov

--001a11425f98042521051fccfbf9--