mesa/docs/release-calendar.csv

25.2,2025-10-01,25.2.4,Eric Engestrom,
,2025-10-15,25.2.5,Eric Engestrom,
,2025-10-29,25.2.6,Eric Engestrom,
,2025-11-12,25.2.7,Eric Engestrom,
25.3,2025-10-15,25.3.0-rc1,Dylan Baker,25.3 branchpoint
,2025-10-22,25.2.0-rc2,Dylan Baker,
,2025-10-29,25.2.0-rc3,Dylan Baker,
,2025-11-05,25.2.0-rc4,Dylan Baker,or 25.3.0 final
docs: update calendar for 25.2.3 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37446> 2025-09-17 17:16:34 +02:00			`25.2,2025-10-01,25.2.4,Eric Engestrom,`
docs/release-calendar: add 25.2.x dates, and 25.3 branchpoint and release candidates I'm having hip surgery (same surgery as last year, other hip) on Oct 22, which I'm hoping goes well and hoping (and expecting) that I'll have recovered enough after a week to be able to sit with my laptop for long enough chunks to do release management. Worst case, if I can't do it I'll push back the 25.2.6 release by a week, but I think I'll keep the branchpoint as that one doesn't take much work as there's nothing to backport, just creating a couple of branches and tags, and setting up a worktree locally which I can do in advance (and have just done so). Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37435> 2025-09-17 12:44:05 +02:00			`,2025-10-15,25.2.5,Eric Engestrom,`
			`,2025-10-29,25.2.6,Eric Engestrom,`
			`,2025-11-12,25.2.7,Eric Engestrom,`
calendar: Update release dates and change 25.3 to Dylan We'll pull the calendar in to regularly scheduled time, and then cut a couple of 25.2 releases we shouldn't need. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37443> 2025-09-17 08:02:11 -07:00			`25.3,2025-10-15,25.3.0-rc1,Dylan Baker,25.3 branchpoint`
			`,2025-10-22,25.2.0-rc2,Dylan Baker,`
			`,2025-10-29,25.2.0-rc3,Dylan Baker,`
			`,2025-11-05,25.2.0-rc4,Dylan Baker,or 25.3.0 final`