[Migration] Moving Jira Issues to GitHub

[Rok Mihevc <ro...@gmail.com>]

Hi,

We have decided to move issue tracking to GitHub [1] and have since
disabled opening new issues on Jira. Next step is copying old issues to
GitHub and locking Jira tracker for comments and changes. Migrated issues
are expected to look more or less as seen here [2].

Work related to this was tracked here [3] and most questions have been
resolved, so I would like to propose to migrate sometime this week. Please
voice any objections.

Rok

[1] https://lists.apache.org/thread/nkzbg0481k0dt0l2wq9b2k60kpg5hk62
[2] https://github.com/datatart/import_dry_run_4/
[3] https://github.com/apache/arrow/issues/14542

More migrated examples here:
https://github.com/datatart/import_dry_run_4/issues/18178
https://github.com/datatart/import_dry_run_4/issues/18190
https://github.com/datatart/import_dry_run_4/issues/18191

Re: [Migration] Moving Jira Issues to GitHub

[Antoine Pitrou <an...@python.org>]

Hi Rok,

I'd like to give my special thanks to you, Todd and everyone else who 
has worked on this. It is the kind of tedious yet essential task that 
helps keep an open source community alive.

Best regards

Antoine.


Le 13/01/2023 à 15:28, Rok Mihevc a écrit :
> Hi all,
> 
> We ran the Jira -> GitHub issue migration on Tuesday. 18292 tickets (2803
> open and 15489 closed) were migrated and can be seen here [1]. Arrow's Jira
> issue tracker is now in read-only mode and all issues received a comment
> linking them to their GitHub counterparts. We strived to keep contents and
> metadata as close to the originals as possible to minimise disruption to
> work of contributors and keep the historical record of work. Comments,
> issue crosslinks, attachments, versions, priorities and labels were
> preserved wherever possible. Authorship is indicated with Jira and GitHub
> usernames.
> 
> Migration did not preserve issue notification settings and even if you are
> tagged in the GitHub issue you will not be notified of changes. You can
> subscribe to GitHub issues you were watching on Jira by running our
> subscription transfer script [2].
> 
> To read more about the work done see the migration umbrella issue [3].
> I would like to thank everybody who worked on this for the past two months.
> Preparing this migration was a real community effort!
> 
> 
> [1] https://github.com/apache/arrow/issues?q=is%3Aissue+author%3Aasfimport
> [2]
> https://github.com/rok/arrow-migration/blob/main/transfer_arrow_subscriptions.py
> [3] https://github.com/apache/arrow/issues/14542
> 

Re: [Migration] Moving Jira Issues to GitHub

[Rok Mihevc <ro...@gmail.com>]

Hi all,

We ran the Jira -> GitHub issue migration on Tuesday. 18292 tickets (2803
open and 15489 closed) were migrated and can be seen here [1]. Arrow's Jira
issue tracker is now in read-only mode and all issues received a comment
linking them to their GitHub counterparts. We strived to keep contents and
metadata as close to the originals as possible to minimise disruption to
work of contributors and keep the historical record of work. Comments,
issue crosslinks, attachments, versions, priorities and labels were
preserved wherever possible. Authorship is indicated with Jira and GitHub
usernames.

Migration did not preserve issue notification settings and even if you are
tagged in the GitHub issue you will not be notified of changes. You can
subscribe to GitHub issues you were watching on Jira by running our
subscription transfer script [2].

To read more about the work done see the migration umbrella issue [3].
I would like to thank everybody who worked on this for the past two months.
Preparing this migration was a real community effort!


[1] https://github.com/apache/arrow/issues?q=is%3Aissue+author%3Aasfimport
[2]
https://github.com/rok/arrow-migration/blob/main/transfer_arrow_subscriptions.py
[3] https://github.com/apache/arrow/issues/14542