How I’d restructure the Minecraft update roadmap

1. Team structure

Split development into two dedicated groups:

• Core Team (~70%): responsible for the annual major update
• Live Team (~30%): responsible for smaller drops, bug fixes, and optimization

Each team operates independently to avoid conflicts in priorities.

2. 2. One major update per year
   • Release window: October to December
   • Scope: large, cohesive changes with full development time
   • Focus on completeness rather than frequency

   ---

   3. • Post-release drops

      After the main update:

      • Smaller updates released periodically
      • Include community-requested features
      • Address bugs and performance issues

      These updates are limited in scope to maintain stability.

   4. Minecraft Live timing and structure

   5. Timing: beginning of the year

      Structure:

      • Recap of the previous update and feedback
      • Presentation of technical improvements and partnerships
      • Early preview of the next major update (subject to change)