[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: Bert Huijben <bert_at_qqmail.nl>
Date: Wed, 16 Sep 2015 13:07:28 +0200

Just noting: The issue tracker we used on tigris is based on Scarab, not on bugzilla.

So we are not converting from bugzilla... Bugzilla is just another option that would need a different migration.


-----Original Message-----
From: "Johan Corveleyn" <jcorvel_at_gmail.com>
Sent: ‎16-‎9-‎2015 12:08
To: "Ivan Zhakov" <ivan_at_visualsvn.com>
Cc: "Stefan Hett" <stefan_at_egosoft.com>; "Stefan" <luke1410_at_posteo.de>; "Daniel Shahaf" <d.s_at_daniel.shahaf.name>; "Julian Foad" <julianfoad_at_btopenworld.com>; "Bert Huijben" <bert_at_qqmail.nl>; "dev" <dev_at_subversion.apache.org>
Subject: Re: Migrating Subversion issues to ...

On Wed, Sep 16, 2015 at 11:59 AM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
> On 16 September 2015 at 11:32, Stefan Hett <stefan_at_egosoft.com> wrote:
>> Hi,
>>>> Speaking about Ivan's suggested monospace-renderer-plugin and the concern
>>>> that it might break with a future version of JIRA: My experience with
>>>> JIRA
>>>> (which dates back to around 2005 I guess) is that Atlassian is quite
>>>> reluctant with introducing changes which break plugins. So it's quite
>>>> rare
>>>> that that a plugin which works in 6.0 breaks during the 6.x releases.
>>>> Things
>>>> are slightly different when the major version numbers change, but then
>>>> this
>>>> only happens every 2 years or so. Hence the maintenance work for such a
>>>> plugin should be considered quite low in the general case.
>>>> On the other side Atlassian requires plugin developers to maintain and
>>>> test
>>>> their plugins on a regular basis (so they are still ensured to be
>>>> compatible
>>>> with later versions).
>>>> If that's some concern and there is some help wanted/needed, I'd be
>>>> willing
>>>> to offer Ivan a hand with the maintenance work on his plugin (if that
>>>> would
>>>> help). As a test environment I'd provide my own JIRA instance, so that
>>>> would
>>>> not add much workload to me.
>>> Thanks for offering help, but I already have test JIRA instance at my
>>> office that I used for Serf project issues migration.
>>> Btw do you have any experience in writing JIRA plugins? Writing
>>> monospaced (preformated) text render would be big help.
>> Unfortunately not at all, otherwise I would have offered to do so.
>> While I do have some decent knowledge of Java due to my studies, I haven't
>> been coding in Java for several years now and don't even have a development
>> environment set-up for that.
> I also don't have Java environment, while I developed several plugins
> more then 10 years ago.
> Link to the Atlassian tutorial if ever want to learn it:
> https://developer.atlassian.com/docs/getting-started/set-up-the-atlassian-plugin-sdk-and-build-a-project

I think we're almost there: I don't think we need a custom renderer or
plugin. Apparently, we can get what we want by enclosing everything
coming from bugzilla within: {noformat:nopanel=true}

That way, we still have the option of using the normal rendering for
new issues (or even editing old issues to move "nicer parts" out of
the noformat block), and only put inside a noformat block the things
which really need to be monospaced.

See here for an example:

Received on 2015-09-16 13:07:49 CEST

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