Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

It Takes a Village to Make WordPress

3,480 views

Published on

In this session, Drew will be sharing insight into how a WordPress release happens, including an overview of all the moving parts, teams, organization, and execution. A lot of people have this idea that the core team is solely responsible for new versions of WordPress getting released, which couldn’t be further from the truth – it’s an intricate ballet of multiple contributor teams coming together and executing a broad vision.
He will talk about how a release cycle is structured, how and where the decision-making happens, as well as all of the various contributors and teams that play their own part in a successful release. It’s very much opening the black box of how a release works.

Published in: Education
  • Be the first to comment

It Takes a Village to Make WordPress

  1. 1. It Takes a Village to Make WordPress Drew Jaynes WordCamp Cape Town 2015
  2. 2. • Platform Engineer at 10up • Docs Committer for WordPress core • 4.2 Release Lead • Developing with WordPress since 2009 • Slides: http://drewf.us/wcct-village Hi, I’m Drew.
  3. 3. How WordPress is Made
  4. 4. How is it really made?
  5. 5. Who are these contributors?
  6. 6. • Developers, designers, UX experts, power users • People who work with/on WordPress full-time, part-time, paid, unpaid • WordPress every day Contributors
  7. 7. Vision
  8. 8. • Release vs Project vision • Advisors / backup lead(s) • Feature plugin proposals Vision
  9. 9. • Release date • April, August, Decemeber • Considerations: support availability, polyglots, holidays Vision
  10. 10. • Is the feature plugin finish-able? • Does it fit the release and project vision? • Does it satisfy the 80/20 rule? Vision
  11. 11. Kickoff
  12. 12. • Schedule • Community feedback • 5 + 6 + 2 weeks • Weekly meetings / scrubs Vision • Kickoff
  13. 13. • Beta • Release Candidate • Buffer Vision • Kickoff
  14. 14. Development
  15. 15. • Feature plugins • Bug fixing • Enhancements • Fourth Vision • Kickoff • Development
  16. 16. • Feature plugin merge • Core mentors • Beta triage Vision • Kickoff • Development
  17. 17. Testing: Beta(s)
  18. 18. • 2-4 Betas • Punting enhancements / triage • Triaging priorities • Beta tester plugin / trywpbeta.com Vision • Kickoff • Development • Testing (Beta)
  19. 19. Testing: Release Candidate(s)
  20. 20. • 2+ Release candidates • 0 tickets • Small changes • Two-committer policy Vision • Kickoff • Development • Testing (Release Candidate)
  21. 21. • Start: About page • Start: Version article • Start: Release video Vision • Kickoff • Development • Testing (Release Candidate)
  22. 22. Freeze
  23. 23. • “Soft” string freeze • Finish About page • “Hard” string freeze • Translating subtitles Vision • Kickoff • Development • Testing • Freeze
  24. 24. • Finish: Release video • OMGWTFBBQ post Vision • Kickoff • Development • Testing • Freeze
  25. 25. Launch
  26. 26. • Finish: Version article • Support heads-up • Publish: Video Vision • Kickoff • Development • Testing • Freeze • Launch
  27. 27. • Package / test the release • Release • Announcement post & tweet Vision • Kickoff • Development • Testing • Freeze • Launch
  28. 28. Post-Launch
  29. 29. • Retrospective • Documentation • Downtime • Post Launch
  30. 30. Resources
  31. 31. • Core Development Blog • Feature Plugins page • WordPress Slack • Core Trac Resources
  32. 32. Questions? Drew Jaynes | @DrewAPicture Slides: http://drewf.us/wcct-village

×