We definitely should create a 4.0 branch and trunk becomes 4.1. I think
there should be instructions in the build/README but it's been so long
since we switched from 3.3 to 3.4, I'm not sure.
One con is that we do need to get masscheck and various tools on the
server to work with the new 4.0 release. I'm not sure my eyesight is
good enough to do it anymore but I'm happy to help!
I would definitely be +1 for Git.
Regards,
KAM
On 12/17/2022 3:42 PM, Sidney Markowitz wrote:
Now that we have released 4.0.0, we can if we want create a 4.0 branch
and have trunk be for a 4.1 branch.
Pros: If we do it now, then if something comes up that is important
enough to require a 4.0.1 patch release, we will not have commits
already in svn that are not suitable for being 4.0.1, either because
they are not yet finished, or not tested, or too extensive. We can
only commit to the 4.0 branch things that are completed and tested and
deemed safe enough that 4.0 branch will always be stable and available
for a 4.0.1 release if the need arises. Branching now means we don't
have to worry that what we commit to trunk may end up unsuitable for a
future 4.0 branch.
Cons: Until someone actually works on something that we would want in
4.1.0 and not in a hypothetical 4.0.1, we have to consider every
commit to trunk and replicate it in the 4.0 branch. We could instead
put off branching until there is something to commit to trunk that we
might not want in 4.0.1 or that would have to be reverted as part of
the process of creating a branch.
Thoughts on this? Branch now or branch later?
Sidney
--
Kevin A. McGrail
kmcgr...@apache.org
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
