STEP:Update Procedure BB Code
From Step Mods | Change The Game
[b]Update Procedure[/b] (revised July 6th, 2014) [b]All tools and actions can be accessed via [url=https://stepmodifications.org/wiki/STEP:Main]the STEP Portal[/url].[/b] [color=#00ffff][b]WIKI WORKFLOW[/b][/color] [LIST=1] [*][color=#ffda00]Check that the DevelopmentRelease version corresponds to the actual development release![/color] This can happen when we set it at the time of the previous release, expecting v2.2.x, but instead release an interim version like 2.2.x.x. If this is not set correctly, then the following will not behave as expected! Edit STEP:Main, changing the DevelopmentRelease number at the bottom of the page to the current dev release number ... change NOTHING else at this point![/*] [*]Copy over new STEP Guide if necessary. (STEP Portal: COPY DEVELOPMENT GUIDE)[/*] [*]Copy to a new dev changelog page for the next release. (STEP Portal: COPY DEVELOPMENT CHANGELOG)[/*] [*]Propagate new Mod List. (STEP Portal: EDIT/PROPAGATE MOD LISTS)[/*] [*]Create mod pages for all new [color=#00ff00]Accepted[/color] mods (full detail + gallery where applicable; [color=#ffda00]USE THE THREAD NAME for the Mod page name[/color], excluding the author portion of the topic name)[/*] [*]Ensure all new STEP:Core mods have the "Core" attribute ticked on the relevant mod page. Likewise, un-tick the "Core" mod attribute on any mod pages that are removed from STEP:Core and/or from STEP entirely. (NOTE: This will affect the current live Guide, so it's best to do this at the last minute before release) (HINT: See the 'Core' indicators --or lack thereof-- in the newly-propagated development STEP Guide [STEP Portal: COPY DEVELOPMENT GUIDE ([color=#00ffdd]edit[/color])]to determine which mods are currently considered 'Core' and which are not and modify accordingly)[/*] [*]Ensure any mods which were [color=#daa520]moved[/color] have had their STEP Section changed on their mod page.[/*] [*]Final edit the propagated Mod List according to the dev changelog (STEP Portal: EDIT/PROPAGATE MOD LISTS)[/*] [*]Check, double-check, and finalize the dev changelog!!! (STEP Portal: COPY DEVELOPMENT CHANGELOG (edit)[/*] [/LIST] [color=#00ffff][b]FORUM WORKFLOW[/b][/color][/*] [LIST=1] [*]Ensure that all new [color=#00ff00]Accepted[/color] topics are named properly ... "[b][color=#ffda00]Nexus mod full name (by Author)[/color][/b]"[/*] [*]Ensure that all new [color=#00ff00]Accepted[/color] topic's OPs are formatted with the Anthology Boilerplate. (STEP Portal: ANTHOLOGY BOILERPLATE)[/*] [*]Ensure the [color=#ffff00]Testing[/color] tag has been removed from all new Accepted mods (From the Topic view, tick the box at right of the [color=#00ff00]Accepted[/color] topic, then select "Unmark for Testing" from the menu in the tool pop-up at lower right)[/*] [LIST] [*]If pinned, unpin each [color=#00ff00]Accepted[/color] topic using the pop-up tool from the topic view (otherwise, it will remain pinned in the Mods forum, which is undesirable)[/*] [*]Move [color=#00ff00]Accepted[/color] mods to the Anthology using the the pop-up tool from the topic view (Be sure to tick the box to leave a redirect to help prevent redundant threads from being created in the future.)[/*] [*]Mods not Accepted can keep their [color=#ffff00]Testing[/color] tag if testing is planned to continue for next release; else, the [color=#ffff00]Testing[/color] tag should be removed for mod not planned for further testing.[/*] [*]Ensure all mods that were dropped from STEP have been tagged as "[color=#b22222]Dropped[/color]" within the Anthology forums (see 'finalized' development changelog for reference) ... please DO NOT move Dropped mod topics back into the Mods forum![/*] [*]Ensure any mods which were [color=#daa520]moved[/color] (see 'finalized' development changelog for reference) are likewise moved to the appropriate subforum within the Anthology.[/*] [/LIST][/LIST] [color=#00ffff][b]NEXUS WORKFLOW[/b][/color][/*] [LIST=1] [*]Propagate and edit the development versions of Nexus Description source, Email source, and Nexus File source. To do this use the "Edit/Create New" links from STEP:Main and make all necessary edits to the dev release source. The links highlighted below will propagate new development versions if the page does not yet exist (or has been deleted), whereas the actual label links will link to edit the current release source when updating that ... so clidk Edit/Create new please :) [/*] [LIST] [*]STEP Portal: Nexus Description ([color=#00ffdd]Edit/Create new[/color])[/*] [*]STEP Portal: Email ([color=#00ffdd]Edit/Create new[/color])[/*] [*]STEP Portal: Nexus File ([color=#00ffdd]Edit/Create new[/color])[/*] [/LIST][/LIST] [color=#00ffff][b]MISCELLANEOUS WORKFLOW[/b][/color][/*] [LIST=1] [*]Ensure the STEP Patches are updated for current release. EssArrBee?[/*] [*]Ensure all BCFs are up-to-date for current mod versions (if not; comment them out until they are. See here: [url=https://www.w3schools.com/tags/tag_comment.asp]W3Schools[/url]). This may no longer apply, since we are only supporting MO at this stage.[/*] [*]Ensure all STEP provided FOMODs are up-to-date for current mod versions (if not; contact [url=https://stepmodifications.org/forum/user/326-techangel85/]Tech[/url] to update them.).[/*] [/LIST] [b][color=#00ffff]Just Prior to Release[/color][/b] (needs to be completed all at once!)[/*] [LIST=1] [*]Update STEP:Main by updating PreviousRelease and CurrentRelease AND DevelopmentRelease accordingly[/*] [*][url=https://stepmodifications.org/wiki/index.php?title=STEP:Guide&redirect=no]Change the redirect[/url] to point users to the new Guide.[/*] [*][url=https://stepmodifications.org/forum/forum/5-releases/]Close old bug reports topic[/url] and start new one (edit accordingly to point to new [i]release [/i]changelog).[/*] [*][url=https://stepmodifications.org/forum/forum/48-step-current-release-development/]Close old dev topic[/url] and start new one (edit accordingly to point to new [i]dev [/i]changelog).[/*] [*][url=https://stepmodifications.org/forum/forum/4-announcements/]Post release announcement[/url] on forums.[/*] [*]Nexus and Email:[/*] [LIST] [*]Copy the Nexus Description source to the Nexus[/*] [*]Upload the updated Patches (see [url=https://github.com/EssArrBee/STEP-Patches]GitHub)[/url] with the appropriate [url=https://stepmodifications.org/wiki/Category:Nexus_File_Attributes]File Attributes[/url].[/*] [*]Send out a mass mail ([url=https://stepmodifications.org/wiki/Category:Email]Email source[/url]) from the AdminCP. (email can only be sent my Admin)[/*] [*]Create new entries of the Nexus Description, File Attributes, and Email for the development version.[/*] [/LIST][/LIST]
