Difference between revisions of "Map release process"

From QWiki
(Created page with "--DRAFT--<br> This page is aimed at mappers that want to release their creations, an expect them to be used in tournaments.<br> <br> The process is expected to solve problems...")
 
Line 12: Line 12:
  
  
==Process==
+
==Map release process==
 +
[[File:Qw-map-release.drawio.png|frame|left]]
 
===Step 1. Closed beta===
 
===Step 1. Closed beta===
 
* The map is mostly ready, and this is the stage where the mapper wants to start collecting feedback.
 
* The map is mostly ready, and this is the stage where the mapper wants to start collecting feedback.

Revision as of 16:52, 20 May 2024

--DRAFT--

This page is aimed at mappers that want to release their creations, an expect them to be used in tournaments.

The process is expected to solve problems associated with map releases (inconsistent names, artifacts, long period until the final is released, etc.).

Goals

Having a documented set of steps for map releases aims to

  1. Establish recommended steps for consistent map releases;
  2. Collect feedback in an orderly matter;
  3. Haste the final release ensuring the highest quality.


Map release process

Qw-map-release.drawio.png

Step 1. Closed beta

  • The map is mostly ready, and this is the stage where the mapper wants to start collecting feedback.
  • The map should be sent privately to the beta testers.
  • The number of beta testers should be limited - 3 should be enough
  • The map name (file) should have the suffix _beta1 (can be multiple)

Step 2. Collect feedback

  • the beta testers provide feedback.
  • the map is changed / upgraded, and it can be another closed beta version OR it can be a Release Candidate.

Step 3. Release candidate

  • the map is released to the public for the first time. Until this moment, the map was unknown to the public.
  • The map name (file) should have the suffix rc1 (can be multiple)
  • the public provides feedback (see section below)

Step 4. Collect feedback

  • the public provide feedback.
  • the map is changed / upgraded, and it can be another Release Candidate, or the Final version.

Step 5. Final release

  • The mapper decides to make the final release.
  • Between step 3 and this step there should be a period no longer than 30 days.
  • The Artifacts mentioned below should be included with the release. They should be worked on before the release.


Collecting feedback

Google sheets/forms can be used. Link to template to be added later


Artifacts

The map release should include the following artifacts:

  • BSP file (uploaded to https://maps.quakeworld.nu/)
  • loc file (uploaded to https://maps.quakeworld.nu/)
  • Wiki page of the map (info + links to everything)
  • top view of the map, including major items (added to the Wiki page)
  • MAP file (optional) (its the source of the map)
  • Small presentation video (optional)
  • high resolution textures (optional)