Important! Redmine issue migration

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Important! Redmine issue migration

Fields, Christopher J
I (finally!) have a set of tools working to migrate Bioperl issues from the old bug report system (https://redmine.open-bio.org) to Github Issues.  You can see a test run of this here:


Note this points back to the original Redmine repo.  We’ll keep that operational since it has attachments present for some tickets, but for any future work the link will become read-only (and may go away in the future as we phase out the Redmine repo).

As for the migrated issues, we’ll likely keep this as a separate (empty) repository for the time being (I will change the ownership to 'bioperl' once it looks fine).  This is primarily to ensure we don’t clutter or munge up the main bioperl-live repo Issues already in place, since we can’t delete Github issues once they are created.  I will be adding a placeholder ticket pointing to them within the bioperl-live ticket system for the time being.  

The important part: once the test run is finished, we could implement the user map; however, old bioperl users/contributors may see a flood of Github emails if you submitted or replied to any ticket in the past.  We do not have to implement this functionality, in fact I’m reluctant to spam past contributors unless we see an overwhelming need to do so (particularly since we can simply add their Github user ID to a comment if needed).  So my official position is that we won’t map Github users to tickets, except manually via comments and only when necessary.  Welcome to any dissenting opinions.

Thanks!

chris



_______________________________________________
Bioperl-l mailing list
[hidden email]
http://mailman.open-bio.org/mailman/listinfo/bioperl-l
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Important! Redmine issue migration

Hilmar Lapp-5
That's fantastic Chris! Long awaited that someone take this on. I agree that tagging the original submitters suffices. Though perhaps that's what you're arguing _not_ to do?

I do think it's a reasonable assumption that someone who submits an issue by default wants to stay in the loop about its resolution. Tagging the submitter's GitHub account would accomplish that.

-hilmar

Sent from away

On Sep 24, 2015, at 11:39 PM, Fields, Christopher J <[hidden email]> wrote:

I (finally!) have a set of tools working to migrate Bioperl issues from the old bug report system (https://redmine.open-bio.org) to Github Issues.  You can see a test run of this here:


Note this points back to the original Redmine repo.  We’ll keep that operational since it has attachments present for some tickets, but for any future work the link will become read-only (and may go away in the future as we phase out the Redmine repo).

As for the migrated issues, we’ll likely keep this as a separate (empty) repository for the time being (I will change the ownership to 'bioperl' once it looks fine).  This is primarily to ensure we don’t clutter or munge up the main bioperl-live repo Issues already in place, since we can’t delete Github issues once they are created.  I will be adding a placeholder ticket pointing to them within the bioperl-live ticket system for the time being.  

The important part: once the test run is finished, we could implement the user map; however, old bioperl users/contributors may see a flood of Github emails if you submitted or replied to any ticket in the past.  We do not have to implement this functionality, in fact I’m reluctant to spam past contributors unless we see an overwhelming need to do so (particularly since we can simply add their Github user ID to a comment if needed).  So my official position is that we won’t map Github users to tickets, except manually via comments and only when necessary.  Welcome to any dissenting opinions.

Thanks!

chris


_______________________________________________
Bioperl-l mailing list
[hidden email]
http://mailman.open-bio.org/mailman/listinfo/bioperl-l

_______________________________________________
Bioperl-l mailing list
[hidden email]
http://mailman.open-bio.org/mailman/listinfo/bioperl-l
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Important! Redmine issue migration

Fields, Christopher J
The move will have to be iterative; I seem to have hit a submission limit which forbids sending more than a few hundred queries/updates.  Not sure why, as it’s done via OAuth key.  Not a big problem, just will be in 2-3 batches.

I may do a quick test run to see whether the submitter alone is mapped to the Github ID or if it’s also commenter IDs.  If someone is being pinged for every mention of their name in comments it might get loud :)

chris

On Sep 25, 2015, at 7:03 AM, Hilmar Lapp <[hidden email]> wrote:

That's fantastic Chris! Long awaited that someone take this on. I agree that tagging the original submitters suffices. Though perhaps that's what you're arguing _not_ to do?

I do think it's a reasonable assumption that someone who submits an issue by default wants to stay in the loop about its resolution. Tagging the submitter's GitHub account would accomplish that.

-hilmar

Sent from away

On Sep 24, 2015, at 11:39 PM, Fields, Christopher J <[hidden email]> wrote:

I (finally!) have a set of tools working to migrate Bioperl issues from the old bug report system (https://redmine.open-bio.org) to Github Issues.  You can see a test run of this here:


Note this points back to the original Redmine repo.  We’ll keep that operational since it has attachments present for some tickets, but for any future work the link will become read-only (and may go away in the future as we phase out the Redmine repo).

As for the migrated issues, we’ll likely keep this as a separate (empty) repository for the time being (I will change the ownership to 'bioperl' once it looks fine).  This is primarily to ensure we don’t clutter or munge up the main bioperl-live repo Issues already in place, since we can’t delete Github issues once they are created.  I will be adding a placeholder ticket pointing to them within the bioperl-live ticket system for the time being.  

The important part: once the test run is finished, we could implement the user map; however, old bioperl users/contributors may see a flood of Github emails if you submitted or replied to any ticket in the past.  We do not have to implement this functionality, in fact I’m reluctant to spam past contributors unless we see an overwhelming need to do so (particularly since we can simply add their Github user ID to a comment if needed).  So my official position is that we won’t map Github users to tickets, except manually via comments and only when necessary.  Welcome to any dissenting opinions.

Thanks!

chris


_______________________________________________
Bioperl-l mailing list
[hidden email]
http://mailman.open-bio.org/mailman/listinfo/bioperl-l


_______________________________________________
Bioperl-l mailing list
[hidden email]
http://mailman.open-bio.org/mailman/listinfo/bioperl-l
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Important! Redmine issue migration

Fields, Christopher J
Just an update: I’m working on the final migration now.  I’ve enabled user name mapping to github IDs for the original bug reports (but not the comments, which should cut down on noise).  Once this is finished I’ll reassign the redmine issues repo over to the bioperl organization. I’ll also check the bioperl-run and other bioperl-* repos on redmine to see how many tickets are left.

chris

On Sep 28, 2015, at 9:25 PM, Fields, Christopher J <[hidden email]> wrote:

The move will have to be iterative; I seem to have hit a submission limit which forbids sending more than a few hundred queries/updates.  Not sure why, as it’s done via OAuth key.  Not a big problem, just will be in 2-3 batches.

I may do a quick test run to see whether the submitter alone is mapped to the Github ID or if it’s also commenter IDs.  If someone is being pinged for every mention of their name in comments it might get loud :)

chris

On Sep 25, 2015, at 7:03 AM, Hilmar Lapp <[hidden email]> wrote:

That's fantastic Chris! Long awaited that someone take this on. I agree that tagging the original submitters suffices. Though perhaps that's what you're arguing _not_ to do?

I do think it's a reasonable assumption that someone who submits an issue by default wants to stay in the loop about its resolution. Tagging the submitter's GitHub account would accomplish that.

-hilmar

Sent from away

On Sep 24, 2015, at 11:39 PM, Fields, Christopher J <[hidden email]> wrote:

I (finally!) have a set of tools working to migrate Bioperl issues from the old bug report system (https://redmine.open-bio.org) to Github Issues.  You can see a test run of this here:


Note this points back to the original Redmine repo.  We’ll keep that operational since it has attachments present for some tickets, but for any future work the link will become read-only (and may go away in the future as we phase out the Redmine repo).

As for the migrated issues, we’ll likely keep this as a separate (empty) repository for the time being (I will change the ownership to 'bioperl' once it looks fine).  This is primarily to ensure we don’t clutter or munge up the main bioperl-live repo Issues already in place, since we can’t delete Github issues once they are created.  I will be adding a placeholder ticket pointing to them within the bioperl-live ticket system for the time being.  

The important part: once the test run is finished, we could implement the user map; however, old bioperl users/contributors may see a flood of Github emails if you submitted or replied to any ticket in the past.  We do not have to implement this functionality, in fact I’m reluctant to spam past contributors unless we see an overwhelming need to do so (particularly since we can simply add their Github user ID to a comment if needed).  So my official position is that we won’t map Github users to tickets, except manually via comments and only when necessary.  Welcome to any dissenting opinions.

Thanks!

chris


_______________________________________________
Bioperl-l mailing list
[hidden email]
http://mailman.open-bio.org/mailman/listinfo/bioperl-l

_______________________________________________
Bioperl-l mailing list
[hidden email]
http://mailman.open-bio.org/mailman/listinfo/bioperl-l


_______________________________________________
Bioperl-l mailing list
[hidden email]
http://mailman.open-bio.org/mailman/listinfo/bioperl-l
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Important! Redmine issue migration

Fields, Christopher J
All tickets have been moved over!  I moved the other project issues right into the project tracker instead of creating a separate repo, e.g. bioperl-db:

https://github.com/bioperl/bioperl-db/issues

We could merge the redmine issues into bioperl-live if needed, though it has way more than the others and was more problematic due to github REST API limits. I have also closed the relevant Redmine project trackers, which makes them read-only.  A number of user names didn’t map, though I don’t think that’s too much of a problem.

chris

On Oct 7, 2015, at 6:17 PM, Fields, Christopher J <[hidden email]> wrote:

…and the bioperl-live tickets are essentially done.  


We can move over the others, and then I can archive the projects on the OBF instance so they are read-only.

chris

On Oct 7, 2015, at 2:57 PM, Fields, Christopher J <[hidden email]> wrote:

Just an update: I’m working on the final migration now.  I’ve enabled user name mapping to github IDs for the original bug reports (but not the comments, which should cut down on noise).  Once this is finished I’ll reassign the redmine issues repo over to the bioperl organization. I’ll also check the bioperl-run and other bioperl-* repos on redmine to see how many tickets are left.

chris

On Sep 28, 2015, at 9:25 PM, Fields, Christopher J <[hidden email]> wrote:

The move will have to be iterative; I seem to have hit a submission limit which forbids sending more than a few hundred queries/updates.  Not sure why, as it’s done via OAuth key.  Not a big problem, just will be in 2-3 batches.

I may do a quick test run to see whether the submitter alone is mapped to the Github ID or if it’s also commenter IDs.  If someone is being pinged for every mention of their name in comments it might get loud :)

chris
...

_______________________________________________
Bioperl-l mailing list
[hidden email]
http://mailman.open-bio.org/mailman/listinfo/bioperl-l
Loading...