On 2022-12-17 at 15:42:08 UTC-0500 (Sun, 18 Dec 2022 09:42:08 +1300)
Sidney Markowitz <sid...@apache.org>
is rumored to have said:
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?
Later, when we have compelling reasons for a 4.1. Is anyone actively
working on things that couldn't go into a 4.0.x release?
As for moving to git, mark me down for a whiny non-binding -0.5. I
recognize that there are sound arguments for doing so, especially in
reducing friction for new contributors. But I will probably never
reshape my brain to be comfortable using git. or to do it right...
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
