[Privoxy-devel] Release date for Privoxy 4.1.0 stable

[Ian Silvester]

To me it depends upon the complexity of adding zstd support. If you feel there's a risk of breakage with that enabled then a beta release has value, but if the addition is simple and clean then 4.1.0 stable makes more sense. 

On Fri, 5 Dec 2025, at 07:27, Fabian Keil via Privoxy-devel wrote:
> Roland Rosenfeld <roland at spinnaker.de> wrote on 2025-12-05 at 12:29:23:
>
>> On Fr, 05 Dez 2025, Fabian Keil via Privoxy-devel wrote:
>> 
>> > The Privoxy version in git master has been 4.1.0 for a while now [0]
>> > and I even looked at the version when writing my mail but apparently
>> > got it wrong twice in a row anyway ...
>> 
>> I also noticed this after writing my previous mail.
>> Maybe we should keep 4.1.0 as beta and release 4.2.0 as the new stable
>
> Do you propose that we create an actual 4.1.0 beta release (tag, test,
> build packages, send out the announcement, update the RSS feed etc.),
> wait a while and then release 4.2.0 stable with basically the same
> code plus eventual fixes?
>
> We did beta releases like this in the past but stopped doing
> so because it wasn't obvious that it was worth the trouble.
>
>> (an alternative option would be 4.1.1 as stable, 4.2.0 feels better,
>> doesn't it?)
>
> Releasing 4.1.1 stable next without having released (announced etc.) an
> actual 4.1.0 version might confuse users, though.
>
> Currently the developer manual explains that "Y, the version minor,
> is increased for every release except for pure bug fix releases in
> which case only Z, the point or sub version, is increased.".
>
> Technically it doesn't say by how much Y is increased so I suppose
> releasing 4.2.0 stable after 4.0.0 stable wouldn't be against the
> rule ...
>
> Fabian
>
> _______________________________________________
> Privoxy-devel mailing list
> Privoxy-devel at lists.privoxy.org
> https://lists.privoxy.org/mailman/listinfo/privoxy-devel