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 5F99617E23 for ; Tue, 15 Sep 2015 11:52:13 +0000 (UTC) Received: (qmail 67608 invoked by uid 500); 15 Sep 2015 11:52:13 -0000 Delivered-To: apmail-subversion-dev-archive@subversion.apache.org Received: (qmail 67560 invoked by uid 500); 15 Sep 2015 11:52:13 -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 67550 invoked by uid 99); 15 Sep 2015 11:52:12 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2015 11:52:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 726621A1EFE for ; Tue, 15 Sep 2015 11:52:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.901 X-Spam-Level: ** X-Spam-Status: No, score=2.901 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id oDwP5S_UpEO0 for ; Tue, 15 Sep 2015 11:52:00 +0000 (UTC) Received: from mail-vk0-f45.google.com (mail-vk0-f45.google.com [209.85.213.45]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id AA43F206E8 for ; Tue, 15 Sep 2015 11:51:59 +0000 (UTC) Received: by vkfp126 with SMTP id p126so77363259vkf.3 for ; Tue, 15 Sep 2015 04:51:52 -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=lXmjXZHVqqPiQFXh6ZcnqDR/YyOZRAn8LHiGxdgLkto=; b=sRayJ81zj/wIR4RjeOSezEurkW9WRl6FOg0Dn6PsK/ZC/nwcKKYPy67CfQ5q5BLxBL ZgjpqEsM6VawzwPj6x++MDbzMwhlVNRt6X/iQXAAB0RzaGkAIX5LYXSNM/zZhHmu7EHX QaF9pVJXyKMwKQgOtmhdquR7tuzz6lqo1zpNHLCsKfJcEhLnbcAXPvf7MHzCSnlHfTzF j2wy9z31cRp3JIKPUMEUQH0gIJlH8w2FoqqZoObsrVF7w2TLTa61Q9ZBWtOUWd3z0Iv2 C1IIcaG9ARgxlElYJq1CblReRd5gO089gpIsrhie0TTW5Q2BhyDIW2UiJsV3o4l7hyuf iB/A== MIME-Version: 1.0 X-Received: by 10.31.160.195 with SMTP id j186mr19972196vke.7.1442317912858; Tue, 15 Sep 2015 04:51:52 -0700 (PDT) Received: by 10.31.180.134 with HTTP; Tue, 15 Sep 2015 04:51:52 -0700 (PDT) In-Reply-To: References: <001201d0ef9d$31ef3a90$95cdafb0$@qqmail.nl> <55F80232.9030704@egosoft.com> Date: Tue, 15 Sep 2015 06:51:52 -0500 Message-ID: Subject: Re: Migrating Subversion issues to ... From: Greg Stein To: Stefan Hett Cc: dev@subversion.apache.org Content-Type: multipart/alternative; boundary=001a11427b74d9669a051fc7ce13 --001a11427b74d9669a051fc7ce13 Content-Type: text/plain; charset=UTF-8 On Tue, Sep 15, 2015 at 6:37 AM, Greg Stein wrote: > On Tue, Sep 15, 2015 at 6:34 AM, Stefan Hett wrote: > >> On 9/15/2015 12:49 PM, Greg Stein wrote: >> >> On Tue, Sep 15, 2015 at 5:12 AM, Ivan Zhakov wrote: >> >>> On 15 September 2015 at 11:59, Bert Huijben < >>> bert@qqmail.nl> wrote: >>> >> >... >> >>> > 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 >>> >> >> +1 to JIRA. (and -0 on tigris; -0.5 bugzilla) >> >> >... >> >>> One option to resolve this would be create JIRA plugin with very >>> simple "field renderer" that uses monospaced font. Field renderer is >>> configured per project, so it's technically possible to use it on >>> shared ASF JIRA installation. The only question is whether ASF infra >>> allow us to install such simple plugin (or develop it for us?). >>> >> >> They already have lots of concerns around the JIRA installation. I >> seriously doubt they'd approve any such plugin, and certainly would not >> develop/test such a thing. I'll go ask ... >> >> Do JIRA comments have any sort of formatting available (eg markdown), to >> do the formatting? >> >> Short answer: yes it has >> From JIRA's feature point of view, it has the same features available as >> the description field or any other custom field you add. That said, it can >> be set to use the text- or the wiki-markup renderer. >> > > Yup. I just found the following page: > > https://confluence.atlassian.com/jira/configuring-renderers-185729478.html > > I don't see "Steps to Reproduce" in there, but we won't be converting any > Tigris issues into that field. We don't need monospace there. ... as long > as we have monospace in Description and Comments, then we're good to go. > > I'd further posit: we can lose some fidelity in the conversion. The above > seems like we'll get 99% > Gavin set up a test/example: https://issues.apache.org/jira/browse/TST-210 --001a11427b74d9669a051fc7ce13 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Sep 15, 2015 at 6:37 AM, Greg Stein <gstein@gmail.com> wr= ote:
On Tue, Sep 15, 2015 at 6:34 AM, Stef= an Hett <stefan@egosoft.com> wrote:
=20 =20 =20
On 9/15/2015 12:49 PM, Greg Stein wrote:
On Tue, Sep 15, 2015 at 5:12 AM, Ivan Zhakov <ivan@visualsvn.com> wrote:
On 15 September 2015 at 11:59, Bert Huijben <bert@qqmail.nl> wrote:
>...=C2=A0
> 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

+1 to JIRA. (and -0 on tigris; -0.5 bugzilla)

>...=C2=A0
One option to resolve this would be create JIRA plugin with very
simple "field renderer" that uses monospaced font. = Field renderer is
configured per project, so it's technically possible to use it on
shared ASF JIRA installation. The only question is whether ASF infra
allow us to install such simple plugin (or develop it for us?).

They already have lots of concerns around the JIRA installation. I seriously doubt they'd approve any such plugin, and certainly would not develop/test such a thing. I'll go ask ...

Do JIRA comments have any sort of formatting available (eg markdown), to do the formatting?
 Short answer: yes it has
From JIRA's feature point of view, it has the same features available as the description field or any other custom field you add. That said, it can be set to use the text- or the wiki-markup renderer.

Yup. I just foun= d the following page:


I don't see "Steps to Reproduce&quo= t; in there, but we won't be converting any Tigris issues into that fie= ld. We don't need monospace there. ... as long as we have monospace in = Description and Comments, then we're good to go.

I'd further posit: we can lose some fidelity in the conversion. The = above seems like we'll get 99%
=C2=A0
Gavin set up a test/exa= mple:=C2=A0https:= //issues.apache.org/jira/browse/TST-210

--001a11427b74d9669a051fc7ce13--