20 Oct
2026
20 Oct
'26
5:34 p.m.
May I suggest: 0. Remove internal use of the to-be-removed libraries. After all, if boost can’t do without it, we can’t expect others to do so. Howard On Oct 20, 2026, at 12:55 PM, Vinnie Falco via Boost <boost@lists.boost.org> wrote:
1. mark the to-be-removed libraries specially on the website 2. then separate those libraries visually (a second list below the primary one, a second grouping) 3. then separate them in the release package "include_legacy/boost" for example 4. then make them a separate release package 5. then stop putting out new releases of legacy libraries