Skip to content

Migrating old Trac tickets to Github issues

Jump to bottom Edit New page
Wesley Bland edited this page Oct 22, 2015 · 5 revisions

Trac will be made read-only as of 13 November, 2015. After this date:

  • Ticket authors will no longer be able to edit their old tickets
  • It's more annoying/difficult to get the ticket description wiki source (you can click on the "Comma-delimited text" link at the bottom of a ticket page)

As such, ticket authors are STRONGLY advised to migrate their tickets to Github before 13 November, 2015.

Overview

Ticket authors are responsible for migrating their own tickets. No tickets will be migrated automatically.

Remember that (public) Github issues will be paired with (private) pull requests:

Overview of MPI Forum usage

Hence, ticket authors will need to both migrate their Trac ticket (which is very much like migrating working group wiki pages), and create a pull request with the actual LaTeX source code changes.

General workflow

The general workflow for Migrating Trac tickets is threefold:

  1. Open a public Github issue

    1. Copy the content from an existing Trac ticket
    2. Make any minor changes to accommodate the different wiki styles
    3. Drag any attachments (e.g., PDFs) into the text pane
      • Github will upload the file and insert Markdown for a link to that file
      • You can move that Markdown link to anywhere in the description field
    4. Select the appropriate label(s) and meeting milestone
    5. Save the Github issue

  2. Open a private Github pull request (this is new; we did not have an equivalent to this in Trac)

    1. Fork the private document repo and clone it
    2. Make a branch for your changes
    3. Commit Latex / file changes to the branch corresponding to the solution in the issue you just filed
    4. Push this branch to your Github fork
    5. Create a pull request against the document private repo and that branch on your private fork

  3. Link the public issue and the private pull request

    1. The easiest way to do this is actually to include a special text sequence in the last commit on your branch, Closes mpi-forum/mpi-standard#ISSUE_NUMBER, where ISSUE_NUMBER is the number that Github assigned to the issue that you filed.

More details

More details on the process of creating a Github issue and corresponding pull request can be found on the Guidelines for New Issues wiki page.

Add a custom footer
Add a custom sidebar
Clone this wiki locally