Simon Josefsson wrote: > Timing wise > maybe it make sense to push out a "snapshot" Git bundle right before you > branch off stable-202501? The Git bundle would then include master up > to that point, and the earlier stable-* branches.
Yes, a day around 2025-01-01 is a reasonable timing for the first git bundle publication. > I suspect it isn't > likely that stable-202406 will receive that many commits after > stable-202501 has been branched off? stable-202407 is meant to be maintained until 2025-06-30. For one year. The bundle would then include a branch whose maintenance just ended (stable-202401) and one whose maintenance is ongoing. One thing is important, though: That these bundles get accompanied by a README that clearly tells that the 2025-01-01 bundle is valid only for releases that were made in 2024 and earlier. If, say, a coreutils release is made in February 2025, there 2025-01-01 bundle will be of no use for that coreutils release, and anyone who wants to have a git bundle for that coreutils release will have to wait until 2026-01-01. We need to make this clear, because if there was a pressure on coreutils (or gettext) to only use gnulib from the past year, that would be a major problem for Gnulib development. Bruno
