A proposal to delay the Boost release for two weeks
We have a small problem. Almost all of the release managers will be AFK for the week after Easter, which is the week when we’re scheduled to release 1.91.0 The current schedule is: 1-Apr: Master branch closed 2-Apr: RC1 created 8-Apr 1.91.0 released (assuming no problems) I propose to move all of those dates back two weeks. 15-Apr: Master branch closed 16-Apr: RC1 created 22-Apr 1.91.0 released (assuming no problems) Comments? — Marshall
No dia 23 de mar. de 2026, às 22:56, Marshall Clow via Boost <boost@lists.boost.org> escreveu:
We have a small problem. Almost all of the release managers will be AFK for the week after Easter, which is the week when we’re scheduled to release 1.91.0
The current schedule is: 1-Apr: Master branch closed 2-Apr: RC1 created 8-Apr 1.91.0 released (assuming no problems)
I propose to move all of those dates back two weeks. 15-Apr: Master branch closed 16-Apr: RC1 created 22-Apr 1.91.0 released (assuming no problems)
Comments?
The review for boost::container::hub is scheduled for Apr 16-26. I don’t think this co-incidence poses any problem, just mentioning it here in case someone thinks it does. Joaquín M López Muñoz
On Mon, Mar 23, 2026 at 4:56 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
We have a small problem. Almost all of the release managers will be AFK for the week after Easter, which is the week when we’re scheduled to release 1.91.0
The current schedule is: 1-Apr: Master branch closed 2-Apr: RC1 created 8-Apr 1.91.0 released (assuming no problems)
I propose to move all of those dates back two weeks. 15-Apr: Master branch closed 16-Apr: RC1 created 22-Apr 1.91.0 released (assuming no problems)
Comments?
— Marshall
I'd prefer the proposed change to the schedule. Tom Kent
participants (3)
-
Joaquín M López Muñoz -
Marshall Clow -
Tom Kent