Roadmap: Difference between revisions
From OuroDev
Line 7: | Line 7: | ||
== Release Goals == | == Release Goals == | ||
First stable release goals: | First stable release goals: | ||
# All servers building | # All servers building, updated to a more modern toolchain | ||
# Game is playable | # Game is playable; catch and resolve major client crashes or bugs | ||
# | # PlaySpan requirement is removed from AccountServer (microtransactions) | ||
# Map server has been given 64bit support | # Map server has been given 64bit support (difficulty to be determined) | ||
# Disable perforce for initial stable release, may focus on removing in the future | # Disable perforce for initial stable release, may focus on removing in the future | ||
# Hardware logging disabled server-side and client-side for security reasons | |||
This is focused on preserving i24 as-is, but providing stability of the codebase and removing anything that requires payment and p4 support. | This is focused on preserving i24 as-is, but providing stability of the codebase and removing anything that requires payment and p4 support. | ||
Latest revision as of 00:57, 2 May 2019
Mission Statement
The Ouroboros Project is an ongoing volunteer effort that is taking a three-pronged approach to making CoH available to the public:
- Actively providing documentation and support for setting up private deployments using released 'i25' binaries and 'i24' source.
- Maintaining and releasing stable builds of the 'i24' client and server, including a public git repo and public bug tracker.
- Providing a public wiki for documentation and transparency.
Release Goals
First stable release goals:
- All servers building, updated to a more modern toolchain
- Game is playable; catch and resolve major client crashes or bugs
- PlaySpan requirement is removed from AccountServer (microtransactions)
- Map server has been given 64bit support (difficulty to be determined)
- Disable perforce for initial stable release, may focus on removing in the future
- Hardware logging disabled server-side and client-side for security reasons
This is focused on preserving i24 as-is, but providing stability of the codebase and removing anything that requires payment and p4 support.
General audience may track progress at https://bugs.ourodev.com
Thank you!
Development Rules
- If you work on new stuff, make your OWN branch, then submit a pull request to the Develop branch. Maintain your own branch separately and always pull from develop before submitting a PR
- Volume 2 should have a core group of dedicated coders enforcing its direction: stability, integration of modern DevOps, simplification of deployment, and bug fixes unrelated to game data. (aka The Menders)
- Community builds should focus on the core code instead of game content. That should honestly be handled separately so that custom servers can be built around custom content and not a custom engine