Move the codelist to the open codelists in the guidance #1214

docs/schema/codelists.md

@@ -21,6 +21,16 @@ Codes are case-sensitive, and are generally provided as English language camelCa
 
 ## Open Codelists
 
+### Release Tag
+
+A contracting process can result in a number of releases of information over time. These must be tagged to indicate the stage of the contracting process they relate to.
+
+```eval_rst
+.. codelisttable::
+   :header-rows: 1
+   :file: ../../build/current_lang/codelists/releaseTag.csv
+```
+
 ### Party Role
 
 The organizations, economic operators or other participants in a contracting process are listed in the [parties section](../reference/#parties). A single party can have one or more roles in the contracting process.
@@ -159,16 +169,6 @@ The extended procurement category codelist is used to provide additional detail
 
 ## Closed Codelists 
 
-### Release Tag
-
-A contracting process can result in a number of releases of information over time. These must be tagged to indicate the stage of the contracting process they relate to. 
-
-```eval_rst
-.. codelisttable::
-   :header-rows: 1
-   :file: ../../build/current_lang/codelists/releaseTag.csv
-```
-
 ### Initiation Type
 
 Contracting processes can be formed under a number of different processes. Currently, only 'tender' is supported in this codelist. Future versions of the standard might support other initiation types. The initiation type is used to provide information to consuming applications on the different blocks of data and releases they can expect from a contracting process.