Central Ready Release Process

ReleaseProcess.txt

h2. Release Checklist

# *QA* will hit smoketest for the tickets (https://central.tri.be/projects/premium-plugins/issues?query_id=924) and confirm that they are working-
# If either of the smoketest tickets fail, *QA** updates the ticket and confirms that the *lead dev* saw those updates/has what they need to proceed-
# *PM* will make sure changelog entries (with appropriate credits to users who reported issues on the forums, following our existing format) are in place-
# *PM* will check that the following changes have been made to the readme.txt file:-
** Version numbers are up to date-
** Latest required version of WP/TEC is up to date-
** Latest WP version tested is current-
** The upgrade notice has the appropriate version number. *Important! this should only be added when it genuinely tells the user something useful* as the same text may then appear in a prominent red alert box on the user's plugin update screen-
** Confirm that all changelogs have creidts to community users if applicable- 
# *Lead Dev* will package the ZIP(s) once QA signs off on smoketest (maybe a good point to also think about uploading the .org files for Core, and Tickets via SVN)-
# *QA* should prioritize the mini-full pass testing using the final ZIP, as early as possible – which can be found here: (http://inside.tri.be/2016/05/03/plugins-zip-testing/) When this is complete QA should update the ticket with a copy of the Zip Testing Spreadsheet to confirm a pass on the required plugins.
# While that is happening, the *PM* should test the update process on staging.theeventscalendar.com (Premium plugins only)-
# If all QA passes - awesome! *QA** should update the ticket and confirm to the *PM*-
# With QA's signoff, *PM* should execute the launch - use the [[Release Process]] wiki as a guide - and confirm in here once we're live-
# *QA** should test the update process post-launch to confirm it's all working smoothly.-
# *Lead Dev* will coordinate merging the latest code back into Current Release Branch by EOD, using Zach + Matt for help as needed.-
# *Support* will publish release notes summarizing what went out in a blog post, then will share that in the following locations:-
** Twitter (m.tri.be link)-
** Facebook (m.tri.be link)-
** Dot-org forum post (only if core was updated)-
** TEC sticky forum post in relevant forums (super sticky if all plugins updated)-
# *Support* will go through all related forum threads to let the users know their fix has shipped, and to thank them for their patience (make sure to also check ON HOLD or DECLINED tickets if appropriate)
# *Support* will share a link to the blog post with the whole support team and makes sure everyone is directing users to it-
# If the core The Events Calendar was released, *Support* asks everyone on the team (via an @channel in #watercooler) to vote WORKS for this build alongside the latest and second-to-latest version of WordPress at the dot-org repo.-
# *Support* will send news of the release to WPmail for inclusion in their next newsletter, if appropriate.-
# *Lead Dev* will regenerate current Docs for TEC.com-
# *PM* will remove any Release Candidate Zips that may have been in place while working on the MR. 
# *PM* will confirm everything is wrapped and will close out this ticket + all related tickets in the Current Secondary Release query 
(https://central.tri.be/projects/premium-plugins/issues?query_id=924), moving them to the appropriate target version in doing so.