Next steps in the 3.4.5 release

[Sidney Markowitz <si...@apache.org>]

Hi everyone,

It's awfully quiet regarding the testing of 3.4.5-rc2. I'm making some 
assumptions in taking the next steps in the final release.

Please, speak up if any of these assumptions are wrong and we should not go on 
to a quick 3.4.5 build and vote.

I assume:

  1. There are people who have been running branch 3.4 in a production 
environment since at least when it was tagged as 3.4.5-rc1 last January (even 
though there was no announcement of 3.4.5-rc1 builds)

  2. The few commits to two minor issues that were committed since then have 
been sufficiently reviewed and are deemed safe.

  3. Enough committers do think that what we have in 3.4.5-rc2 is ready for 
release so nothing is left in the process except to build 3.4.5 and call for a 
release vote.

  4. Nobody has a -1 vote against proceeding with release that they can explai 
with a technical reason.


I'll give this another two days. If there are no negative responses to 
consider, I'll proceed with the next steps in the release by building what we 
currently have as 3.4.5.

Regards,

  Sidney Markowitz
  Chair, Apache SpamAssassin PMC
  sidney@apache.org
  sidney@sidney.com

Re: Next steps in the 3.4.5 release

[Bill Cole <bi...@apache.org>]

Just to confirm:

I have been running 3.4-HEAD for most of the past year on a small 
production system. I am confident that it is solid, and my +1 for the 
last vote was to freeze and release.


On 17 Mar 2021, at 17:10, Sidney Markowitz wrote:

> Hi everyone,
>
> It's awfully quiet regarding the testing of 3.4.5-rc2. I'm making some 
> assumptions in taking the next steps in the final release.
>
> Please, speak up if any of these assumptions are wrong and we should 
> not go on to a quick 3.4.5 build and vote.
>
> I assume:
>
>  1. There are people who have been running branch 3.4 in a production 
> environment since at least when it was tagged as 3.4.5-rc1 last 
> January (even though there was no announcement of 3.4.5-rc1 builds)
>
>  2. The few commits to two minor issues that were committed since then 
> have been sufficiently reviewed and are deemed safe.
>
>  3. Enough committers do think that what we have in 3.4.5-rc2 is ready 
> for release so nothing is left in the process except to build 3.4.5 
> and call for a release vote.
>
>  4. Nobody has a -1 vote against proceeding with release that they can 
> explai with a technical reason.
>
>
> I'll give this another two days. If there are no negative responses to 
> consider, I'll proceed with the next steps in the release by building 
> what we currently have as 3.4.5.
>
> Regards,
>
>  Sidney Markowitz
>  Chair, Apache SpamAssassin PMC
>  sidney@apache.org
>  sidney@sidney.com


-- 
Bill Cole