Changes between Version 129 and Version 130 of ReleaseProcessDraft

Timestamp:

Apr 23, 2018, 11:54:46 PM (6 years ago)

Author:

leper

Comment:

--

ReleaseProcessDraft

@@ -72 +72 @@
 
 === Generate signing key for mods ===
-'''Description:''' [[BR]] The valid mods for the upcoming version should be signed with a new key, and the associated public key must be put in the config for the upcoming version. This can be done as soon as breaking changes in the engine prevents one to use the mods from the last version, but delaying the key change allows one to keep testing the mod downloader, even though downloaded mods are incompatible. To generate the keypair use `minisign -G -p pubkey -s secretkey`. [[BR]]'''Can be completed in phase:''' Development [[BR]]'''Candidates:''' Itms
+'''Description:''' [[BR]] The valid mods for the upcoming version should be signed with a new key, and the associated public key must be put in the config for the upcoming version. This can be done as soon as breaking changes in the engine prevents one to use the mods from the last version, but delaying the key change allows one to keep testing the mod downloader, even though downloaded mods are incompatible. To generate the keypair use `minisign -G -p pubkey -s secretkey`. Try not to override the old keys. [[BR]]'''Can be completed in phase:''' Development [[BR]]'''Candidates:''' Itms
 
 === Start release process ===