Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating and updating the project plan from Perforce #171

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

rptb1
Copy link
Member

@rptb1 rptb1 commented Feb 22, 2023

This branch migrates the MPS project plan from Perforce to Git.

Working on #95 .

Solving #125 (comment) .

@rptb1 rptb1 self-assigned this Mar 14, 2023
@rptb1 rptb1 requested review from thejayps and UNAA008 March 14, 2023 09:20
@rptb1 rptb1 added this to the Perforce Divorce milestone Mar 14, 2023
@rptb1 rptb1 added documentation process To do with process or procedure labels Mar 14, 2023
@rptb1
Copy link
Member Author

rptb1 commented Mar 14, 2023

Version 1.117 plan wasn't recorded. It would not be correct to retrospectively "plan" it, unless we can uncover a plan that was made at the time. @gareth-rees might have some record elsewhere.

@rptb1 rptb1 marked this pull request as ready for review March 14, 2023 10:02
@thejayps thejayps added the critical Will cause failure of the entire project label Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical Will cause failure of the entire project documentation process To do with process or procedure
Projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants