Dev Guide
WebsiteGitHubGitBook
  • 📝Dev Intro
    • Using GitHub
    • Using Unity
    • Licensing
    • File Naming & Organization
      • File Naming
      • File Organization
        • Object Type
  • 📡Networking
    • Introduction to Game Networking
    • FishNet Networking
      • Server
      • Client
      • Server RPC
      • ObserversRPC
      • Network Message
  • 🖊️Guidelines
    • The C# Style Guide
      • Nomenclature
        • Namespaces
        • Classes & Interfaces
        • Methods
        • Fields
        • Parameters
        • Delegates
        • Events
        • Misc
      • Declarations
        • One declaration per source file
        • General class structure
        • Access Level Modifiers
        • Spacing
        • Brace Style
        • Switch Statements
        • Language
        • Common Patterns and Structure
          • Applying attributes on all network related methods.
    • Code Design Definitions
      • Actor
      • System
      • View
      • Events
        • Event Bus
        • Action
      • System Locator
      • Tweening
    • Asset Criteria
      • External Criteria
        • Animations
        • Fonts
        • Models
        • Textures
        • Graphics
        • Audio
      • Importing Criteria
        • 3D Models
        • 3D Animations
        • Textures
        • Graphics
        • Audio
      • Internal Criteria
        • 3D Models
        • 3D Animations
        • Textures
        • Graphics
        • Audio
    • SS3D's coder good practices
    • Code design patterns
  • 📖Guides
    • Application Settings
    • Running the Project
      • Configure your firewall and antivirus
      • Building the game
      • Joining a server
      • Hosting a server
      • Setting up a dedicated server
    • Debugging SS3D
    • Maintainer Guide
      • Pull request review process
    • Testing SS3D
      • Assets audit tests
      • Edit mode tests
      • Play mode tests
        • Inventory test
        • Health tests
    • Working with animations
  • 🛣️Roadmap
    • Releases
Powered by GitBook
On this page
  • Release Versioning
  • Automated Releases

Was this helpful?

Edit on GitHub
Export as PDF
  1. Roadmap

Releases

Defining what a release version means.

Release Versioning

The release naming is defined by gamestate.major.minor.hotfix In which the rules are:

Game State

Refers to the overall state of the game. 0.x.x.x version indicates the game is still in a alpha/beta/pre-complete phase. Once we have reached a point where we have ported over most of the systems and content from ss13, and feel satisfied, we can then move to 1.x.x.x and beyond with new content.

Major

Refers to large milestone. Major milestones are large changes that may span numerous months and PRs.

An example of a major milestone would be several new systems or reworked systems that together make up a large change in how the game feels. Milestones will have their version number in their name. e.g. "0.2 - Milestone Name".

Minor

Refers to small milestones. Minor milestones are usually a single large system or a collection of smaller changes.

An example might be a rework to the health system, or a collection of new content for a couple recently added systems.

Hotfix

Refers to quick fixes post a major or minor release. An example would be a critical bug that was undetected until after release and needs to be quickly fixed.

Any example might be a bug that prevents players from joining and needs to be updated in a release ASAP instead of waiting for the next minor release.

Automated Releases

Soon we will move to automated releases much like many of the SS13 servers and such. First they will likely start off as monthly releases but after we gain a lot of momentum we will eventually move to nightly releases.

These will be registered as hotfix releases. Devs will still be able to push manual releases at anytime for hotfixes as well.

PreviousRoadmap

Last updated 2 years ago

Was this helpful?

🛣️