~/talk

2 Weeks is Too Long - On Demand Feature Deployments with Drupal

Talkat Florida DrupalCamp 2024 · 2024-02-23..02-25· [drupal, developer-experience]
links:none on file
slides:none on file

Argues that two-week release cadence is unnecessary and shows concrete changes: deploy code daily behind feature flags, run isolated PR previews with Pantheon multidev, automate checks with Cypress, and extract marketing forms into a Formik microservice. A client ships ordering API code to production three weeks before go-live and flips the flag during a 20-minute window, avoiding a 16-hour blackout. Uses Drupal config management and cleanup of toggles afterward.

AI-written summary · about

  1. 0:00Introduction and goals
  2. 1:47Sprints and releases history
  3. 5:22Why teams run long release cycles
  4. 7:56Mindsets and inflexible processes
  5. 11:11Breaking the two-week cycle mindset
  6. 13:39Feature-based environments and automation
  7. 16:52Keys to moving faster
  8. 17:13What are feature flags
  9. 19:42Drupal feature flag examples
  10. 22:11Microservices and decoupling
  11. 23:39Success story and benefits
  12. 25:48Drupal landscape and tools
  13. 27:58Q&A on feature flag cleanup
  14. 28:41Q&A on config issues
  15. 30:06Q&A on project types and team alignment
  16. 32:14Q&A on ticket planning and features
  17. 33:16Closing and final thoughts
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.