jira conversion - five points

[Daniel Shahaf <d....@daniel.shahaf.name>]

Several issues in the jira conversion:

1. The 'whiteboard' field isn't converted:
http://subversion.tigris.org/issues/buglist.cgi?status_whiteboard=.&status_whiteboard_type=regexp
Bert suggests it doesn't need to be.
Markus points out we could add it to the "issue description" instead of tossing it.
(I have no strong opinion)

2. The 'url' field isn't converted.  I think it is important: unlike
'whiteboard' it can't be derived from the other fields.  For example,
http://subversion.tigris.org/issues/show_bug.cgi?id=4129#desc17 and
issue #4595 both have links on that field that aren't in any other
field, and shouldn't be lost.  I propose we add the URL (either as
a custom field, or inline in the Description, whichever is easier)

3. "#desc42" intra-issue and external links will be broken.  I suppose
there is nothing we can do to prevent that, and if we wanted to
implement a fix, we could do so easily after the migration, too.

4. Given that an XML export of all issues is only 23MB compressed,
I think we should archive the final XML export on ASF hardware.
(Maybe we can just import it to ^/subversion/archive in the repository?)

5. What mailing list will issue notifications go to?
We already have issues@subversion: https://mail-archives.apache.org/mod_mbox/subversion-issues/

---

So, in summary, I think we should:
- migrate the 'url' field into the description field
- archive the tigris xml export on apache.org

Re: jira conversion - five points

[Ivan Zhakov <iv...@visualsvn.com>]

On 19 September 2015 at 01:27, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> Several issues in the jira conversion:
>
> 1. The 'whiteboard' field isn't converted:
> http://subversion.tigris.org/issues/buglist.cgi?status_whiteboard=.&status_whiteboard_type=regexp
> Bert suggests it doesn't need to be.
> Markus points out we could add it to the "issue description" instead of tossing it.
> (I have no strong opinion)
>
I think it's will be very confusing to add status whiteboard as part
of description, given current values of status whiteboard field.
Adding new custom field does worth it also. I suggest just drop it.

> 2. The 'url' field isn't converted.  I think it is important: unlike
> 'whiteboard' it can't be derived from the other fields.  For example,
> http://subversion.tigris.org/issues/show_bug.cgi?id=4129#desc17 and
> issue #4595 both have links on that field that aren't in any other
> field, and shouldn't be lost.  I propose we add the URL (either as
> a custom field, or inline in the Description, whichever is easier)
>
The URL field is already added to Description field. See SVN-4129 for example:
https://issues.apache.org/jira/browse/SVN-4129

> 3. "#desc42" intra-issue and external links will be broken.  I suppose
> there is nothing we can do to prevent that, and if we wanted to
> implement a fix, we could do so easily after the migration, too.
>
> 4. Given that an XML export of all issues is only 23MB compressed,
> I think we should archive the final XML export on ASF hardware.
> (Maybe we can just import it to ^/subversion/archive in the repository?)
>
+1, but I'm going to do this after migration when issue tracker on
tigris will be read-only.

-- 
Ivan Zhakov

Re: jira conversion - five points

[Daniel Shahaf <d....@daniel.shahaf.name>]

Stefan wrote on Sat, Sep 19, 2015 at 11:52:09 +0200:
> Hi,
> >5. What mailing list will issue notifications go to?
> >We already have issues@subversion:https://mail-archives.apache.org/mod_mbox/subversion-issues/
> That mailing list isn't listed on the mailing-lists page:
> http://subversion.apache.org/mailing-lists.html
> 
> Was it left out intentionally? Should it (or whatever will be set-up
> for JIRA) be listed on that page in the future?

It was probably left out because it hasn't been used.  Yes, of course,
if we start using it, it should be added to that page (and an
announcement made to dev@ to invite people to sbuscribe to it).

I assume we have consensus on using that list (issues@s.a.o) for jira
notifications.  We could also have IRC notifications via ASFBot.

Cheers,

Daniel

Re: jira conversion - five points

[Stefan <lu...@posteo.de>]

Hi,
> 5. What mailing list will issue notifications go to?
> We already have issues@subversion:https://mail-archives.apache.org/mod_mbox/subversion-issues/
That mailing list isn't listed on the mailing-lists page: 
http://subversion.apache.org/mailing-lists.html

Was it left out intentionally? Should it (or whatever will be set-up for 
JIRA) be listed on that page in the future?

Regards,
Stefan