Apple Shifts Release Schedule to Favor Early Coding

Software teams can reallocate build and integration time, as Apple did by extending M1 coding from four to six weeks.

Updated on Nov. 8, 2026 in Remote Work

Apple Shifts Release Schedule to Favor Early Coding

Apple has shifted its iOS 28 development schedule, giving engineers six weeks of coding in the M1 milestone instead of four, with the convergence period cut to two weeks. The change also applies to iPadOS 28 and macOS 28, affecting how Apple's internal teams plan their annual operating system cycle.

Why it matters

The schedule change moves time toward early-stage feature development and away from integration, a trade-off that affects how software teams allocate their coding and testing windows. Employees reportedly favor the change because it gives them more room to create before features are locked down.

The change shifts the M1 stage from a standard split of 4 weeks of coding and 4 weeks of convergence to 6 weeks of coding and 2 weeks of convergence, within an 8-week stage. Apple runs three major milestones (M1, M2, M3) per annual operating system cycle, and the adjustment covers iOS 28, iPadOS 28, and macOS 28.

The players

Apple

Apple is a consumer electronics and software company whose iPhone, iPad, and Mac platforms depend on a disciplined annual operating system release cycle.

Mark Gurman

Mark Gurman is a Bloomberg reporter who covers Apple and is known for reporting on the company's internal product and software plans.

The details

Each development stage normally runs eight weeks, with four weeks of coding followed by four weeks of convergence, the period in which newly developed features are integrated into the operating system. The adjusted M1 stage gives engineers six weeks of coding and feature development before two weeks of convergence. Early-stage engineers therefore gain more time to develop and refine ideas before features are finalized, and the extra early-stage time is intended to improve overall feature quality.

Timeline

  1. The M1 milestone has already passed, so the adjusted coding split is already in effect for the current development cycle.

  2. Mark Gurman reported the schedule change in his Power On newsletter on Sunday, shortly before publication.

Market Landscape

Apple's fixed three-milestone annual cycle has long set the pace for its operating system releases, with each stage following a uniform four-and-four split of coding and convergence. This adjustment departs from that pattern by front-loading the M1 stage, a change that shows how the company is tuning its internal process rather than its public release calendar.

Software leaders managing multi-stage release cycles should review whether their coding and integration windows are balanced against the time early-stage engineers need to refine features. Operations and product planning teams should treat stage-length splits as a tunable lever rather than a fixed calendar convention.

The takeaway

Balancing how long teams spend building features against how long they spend integrating them is a process decision that can shift feature quality, so it is worth examining in your own release planning. Track whether shifts in stage length change integration defects or late-cycle rework as a measurable signal.

Further reading

For how distributed and flexible work structures are shaping software teams, see Remote Work.