2. Version History
Record the evolution of the GDD to ensure key changes are traceable, reversible, and aligned with development milestones.
PRID: gdd-en-2-version-history
VERIFIED
2 min read
On this page
2. Version History
Record the evolution of the GDD to ensure key changes are traceable, reversible, and aligned with development milestones.
2.1 Document Metadata
- Document Title: Game Design Document
- Project Codename:
- Current Version:
- Status: (Draft / Review / Approved / Deprecated)
- Owner:
- Last Updated:
2.2 Change Log
Use semantic versioning (e.g., 0.1.0, 0.2.0 corresponding to milestones) and tag change types (Add / Update / Remove / Fix).
| Version | Date | Author | Sections Affected | Change Summary | Reviewer / Approver |
|---|---|---|---|---|---|
| 0.1.0 | 202X-XX-XX | 3, 4, 9 | Initial GDD Draft | ||
| 0.2.0 | 202X-XX-XX | 4. Gameplay, 6. Levels | Core Gameplay & First Batch Levels | ||
| 0.3.0 | 202X-XX-XX | 5, 7, 8 | Story, Interface, and AI Design Added | ||
| 1.0.0 | 202X-XX-XX | Full Document | Launch Version GDD Finalized |
2.3 Milestone Mapping
Map document versions to key project milestones (Prototype, Alpha, Beta, Launch, etc.).
- Prototype: GDD Version:
- Vertical Slice: GDD Version:
- Alpha: GDD Version:
- Beta: GDD Version:
- Launch: GDD Version:
2.4 Review Process
- Review Frequency: (e.g., Before every major version / Bi-weekly)
- Participants: (Design, Engineering, Art, Operations, Data, Publishing, etc.)
- Review Portal: (Meeting / Collaboration Tool Link)
- Decision Logging: (Meeting Minutes / Issue Tracker / Task System)
2.5 Archive & Branching
- Archive Location: (Git Tag / Wiki History / Document Repository)
- Branching Strategy: (For different platforms or versions, e.g., Global / CN / Lite)
- Deprecated Design Marking: (Mark as Deprecated instead of deleting directly)