Release process

• Ensure all milestoned issues/PRs are closed, or reassign to new milestone
• Verify good Testswarm results (alternatively, run all browsers locally)
• Ensure AUTHORS.txt file is up to date (jquery-release will abort otherwise)
  • Get recent authors with grunt authors
  • Look for bad names/emails and update .mailmap using real data from CLA sheet if needed
  • Run grunt authors again, tack new emails onto AUTHORS.txt
• Do release using instructions at jquery-release project README
  • Be sure to clone a CLEAN copy, don't reuse
  • Target something other than jquery/jquery (like your own fork) for a dry run
• Verify that files were created correctly by jquery-release
  • jquery-VER.js, jquery-VER.min.js, jquery-VER.min.map
  • jquery.js, jquery.min.js, jquery.min.map
  • mscdn-jquery-VER.zip, googlecdn-jquery-VER.zip
• Create draft blog post on blog.jquery.com
  • Highlight major changes and reason for release
  • Add contributor list generated above
  • Add changelog generated above
• Publish post on http://blog.jquery.com
• Tweet the release on http://twitter.com and http://plus.google.com

== beta and release candidates can stop here ==

• Update the shipping version on http://jquery.com home page

git pull jquery/jquery.com
# (Edit to update index.html and download.md here)
git commit
npm version patch
git push origin master
git push --tags origin master

• Email bmcquade@google and paulirish@google for Google CDN
  • Send googlecdn-jquery-a.b.c.zip
• Notify MS CDN via their CDN upload location
  • Contact is damian.edwards@microsoft and Pranav.Rastogi@microsoft
  • Send mscdn-jquery-a.b.c.zip
  • Need to zip the uncompressed and min files then upload to their site
  • Follow up with an email
• Email CDNJS folks ryan@ryankirkman and thomasalwyndavis@gmail
  • Just point them to the CDN copies
• For jsFiddle, tweet @zalun or pm him on IRC (same username) or #jsfiddle