Release Procedure

This document will eventually detail the full release procedure for Spree.

1. All deprecations in the previous release (i.e. things marked with a deprecation warning) are now removable. Ensure that this has happened.
2. Check if TODOs can become TODONEs.
3. Anything that should be deprecated by the next release should be marked with a deprecation warning now. Nothing that people rely on should ever be removed in a patch or minor release without a deprecation warning.
4. ALL BUILDS ARE GREEN.
5. Update the Getting Started guide to specify correct version of Rails.
6. Update all CHANGELOG files
7. Update README with correct branches + Rails versions
8. Update version number in generation message in the following files:
   • SPREE_VERSION
   • cmd/lib/spree_cmd/extension.rb
   • core/lib/spree/core/version.rb
9. Update installer.rb: Ensure spree_auth_devise is updated with a new stable branch if releasing a new minor version.
10. Ditto for extension.rb.
11. Ensure spree_gateway is ditto ^
12. Point places in Spree reference spree_auth_devise to new stable branch.
13. bundle exec rake gem:install
14. gem list spree to verify all the components were built
15. Verify local build with new rails app: Run through a checkout and smoke test it. Click around.
16. Tag git repository
    • (for example: git tag v2.0.1)
17. Update version number in the files above to next version.beta (2.0.2.beta) -- DO NOT TAG
18. Checkout the tag commit
    • git checkout gitref
19. Generate a brand new Rails application, run rails g spree:install and vet that it's OK.
20. Ditto, but run spree install --auto-accept.
21. bundle exec rake gem:release
22. Tag and deploy new versions of the guides
23. Update alerts.spreecommerce.com
24. Update #spree channel topic

Smoke Testing Release

1. Add a product to the cart.
2. Run through the checkout with a check payment.
3. Repeat for a different product with a credit card payment.
4. Sign in to the admin backend and click through.