Re: [Netatalk-admins] Planning the next round of releases

[Ralph B. <sl...@sa...>]

On 4/11/23 23:41, Daniel Markstedt wrote:
> Never mind; I started cherry picking locally on the 3.1 branch and 
> recalled that managing / testing yet another branch is too much of an 
> overhead.

yeah, it adds quite some overhead if we cherry-pick.

> The risk of inadvertently breaking something while cherry picking might 
> be even higher.
> 
> The one truly risky change, I think, is the iniparser 3.x to 4.x version 
> bump, which turned out pretty messily with a bunch of regressions.
> So perhaps one idea would be to revert those changes, tag the release, 
> and then restore them in preparation for a future release (3.2.0?)

ok.

What about labeling MRs that are targetted for a point release with a 
label? I've just created the lable "target-release-3.1" for this. That 
way, when a release is immanent, I can quickly see which MRs might still 
be merged and which not.

-slow