Development Team - Policies & Procedures
  • Development Team
    • Development Team Info
      • Team Leadership
      • Project Scopes
      • Task Processing
      • Git Procedures
      • Server Versioning
    • Non-Disclosure Agreement
    • Beta Team Info
    • Apply For Dev Team
    • Changelog
  • Special Updates
    • 3.5.0 Update
  • Developer Wiki
    • Local Dev Server
Powered by GitBook
On this page
  • Version Control
  • Server Version Control
  • Resource Version Control
  • Servers
  1. Development Team
  2. Development Team Info

Server Versioning

Version Control

Server Version Control

To ensure an organized environment, the live server will be version-controlled in the standard server format, for example 1.0.0. The server version will follow this formatting:

  • The first number will be the current version we're using. This number will only change for significant updates that change most resources or change the way the game is played/experienced.

  • The second number will be for significant changes or resource releases.

  • The third number will be for minor revisions, updates, or fixes.

The server version will always be listed on the Server Version pinned thread in the Task Channel.

Resource Version Control

This generally applies to software developers.

Each script resource and custom vehicle resource must utilize proper resource manifest version control formatting. The manifest should contain a version number. The initial version number should be “1.0.0” and follow this formatting:

  • The first number will be for a significant change to the resource

  • The second number will be for minor changes to the script that is still a significant modification

  • The third number will be for minor revisions and patches.

Servers

The Development Team facilitates these types of servers for FiveM:

  • Live Server - The live servers are any servers where any member can join and patrol or receive training.

  • Development Server - The Development Server is the primary server where developers can test their resources with a larger group. It is also where Beta Team members can test bug reports and new features.

  • Localhost Server - Development Team members will need to set up a localhost server and add the proper repositories. This will allow them to test resources locally before pushing the changes to the development branch.

Last updated 4 months ago