5.0 Release Plan

The following tasks should be completed before the release of 5.0:

• Chronos 3.x released
• All 4.x -> 5.x merges complete
• All 4.next -> 5.x merges complete

On day of release:

• Remove development version notice from the 5.x book branch.
• Write bakery release
• Update app version requirements. Push this commit so it ends up in the zip file.
• Tag cakephp release. The github release creation will likely fail, as app constraints can't be satisfied. We'll account for that later.
• Tag cakephp app release.
• Tag plugin installer release.
• Tag bake release
• Tag debug kit release by @lordsimal
• Tag authentication release by @lordsimal
• Tag authorization release by @lordsimal
• Tag elasticsearch release
• Tag migrations release
• Tag repl release
• Tag twig-view release
• Tag queue release

After release is complete. No hard requirement to be tightly coupled to shipping the new release:

• Update 5.x to be the default book alias
• Update 5.x to be the default api alias.
• Deploy the new website theme.
• Update default branches in all repos
• Create new 6.x branch in all repos (should only be created when needed)

Learnings after 5.0 was released

• cakephp/phinx was completely missed in the list above
  • cakephp/phinx 2.0 was released even though the phinx API is not being considered stable
  • The communication with MasterOdin should have been better
• Check plugin docs are deployed for new major of the respective plugins (e.g. auth plugins)
• Forgot about the acl plugin it was intentional because ACL plugin will not be maintained anymore