[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Migrating Subversion issues to ...

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Tue, 15 Sep 2015 14:22:41 +0200

On 15 September 2015 at 13:51, Greg Stein <gstein_at_gmail.com> wrote:
> On Tue, Sep 15, 2015 at 6:37 AM, Greg Stein <gstein_at_gmail.com> wrote:
>>
>> On Tue, Sep 15, 2015 at 6:34 AM, Stefan Hett <stefan_at_egosoft.com> wrote:
>>>
>>> On 9/15/2015 12:49 PM, Greg Stein wrote:
>>>
>>> On Tue, Sep 15, 2015 at 5:12 AM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>>>>
>>>> On 15 September 2015 at 11:59, Bert Huijben <bert_at_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
>
The problem that {noformat} tag adds scrollbars. See the following
comment as an example:
https://issues.apache.org/jira/browse/TST-210?focusedCommentId=14745334&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14745334

-- 
Ivan Zhakov
Received on 2015-09-15 14:23:16 CEST

This is an archived mail posted to the Subversion Dev mailing list.