Elvas Tower: ORMT - Migrating Bug Reports to GitHub.com - Elvas Tower

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

ORMT - Migrating Bug Reports to GitHub.com from Launchpad.net/or Rate Topic: -----

#1 User is offline   cjakeman 

  • Vice President
  • PipPipPipPipPipPipPipPip
  • Group: ET Admin
  • Posts: 2,857
  • Joined: 03-May 11
  • Gender:Male
  • Location:Peterborough, UK
  • Simulator:Open Rails
  • Country:

Posted 30 December 2022 - 01:09 AM

Looky1173 has revived a suggestion from PerpetualKid that our project's use of Launchpad.net should move to GitHub.com.

He has set out the good reasons for doing so here and completed the work needed to prepare for this. That work includes a script to move the bug reports (about 2,600 active and completed) and insert a link into each message indicating its new location.

It's great to have such an effective contribution - thanks Looky1173 - so the Open Rails Management Team (ORMT) are going to go ahead with this.

The steps involved are:
  • test Looky's migration tool by writing to the Open Rails test repo
  • use the migration tool for real
  • add a general message at Launchpad.net to direct users to GitHub.com
  • change the code that takes the user to Launchpad.net after a fatal error
  • change the links on the openrails.org website
  • change the links in our GitHub.com entry
  • change the references in the Manual
  • change the triage code (a script that checks the status of each Pull Request and compares it with bug reports)


#2 User is offline   cjakeman 

  • Vice President
  • PipPipPipPipPipPipPipPip
  • Group: ET Admin
  • Posts: 2,857
  • Joined: 03-May 11
  • Gender:Male
  • Location:Peterborough, UK
  • Simulator:Open Rails
  • Country:

Posted 11 February 2023 - 09:31 AM

I'm pleased to report from the recent ORMT session that progress has been made on much of this process:

The steps done:
  • test Looky's migration tool by writing to the Open Rails test repo
  • change the code that takes the user to Launchpad.net after a fatal error
  • change the links on the openrails.org website
  • change the links in our GitHub.com entry
  • change the references in the Manual

Steps still to do:
  • change the Contributing document on GitHub
  • change the triage code (a script that checks the status of each Pull Request and compares it with bug reports)
  • use the migration tool for real
  • add a general message at Launchpad.net to direct users to GitHub.com and block creation of new bug reports there


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users