On 2022-12-18 14:01, Sidney Markowitz wrote:
3. We don't have a compelling reason to have to move to git, nor do we
have committers clamoring to move to git, nor do we have a total
consensus to move to git.
+1 Change for changes sake? SVN might be a lower barrier to entry for
contributors..
Henrik K wrote on 19/12/22 5:43 am:
Mass check runs from trunk, there are no ties to any specific version, aside
from testing built rules.tar.gz with all 3.4 and 4.0 releases.
It seems like
1. Branching svn would not impact mass check, which will continue to run
from trunk
2. If we ever
Mass check runs from trunk, there are no ties to any specific version, aside
from testing built rules.tar.gz with all 3.4 and 4.0 releases.
On Sun, Dec 18, 2022 at 08:51:29AM -0500, Kevin A. McGrail wrote:
> I don't think a branch would break things but my memory is that mass check is
> built
I don't think a branch would break things but my memory is that mass check
is built on 3.4 specifically. I think a lot of scripts and whatnot need to
be updated.
I am not a resource that remembers this just from a decade or so ago when I
rebuilt the server. Henrik rebuilt it more recently so he
Henrik K wrote on 18/12/22 8:18 pm:
This is atleast third discussion of the same? All the previous times it was
concluded that branching wasn't necessary. Backporting is a pain and
usually something is forgotten. It's not like we have any real developing
going on, does anyone even have a
On Sun, Dec 18, 2022 at 09:42:08AM +1300, 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
Kevin A. McGrail wrote on 18/12/22 3:45 pm:
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!
Questions:
If I were to go ahead and branch, would that
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
On 2022-12-17 at 15:42:08 UTC-0500 (Sun, 18 Dec 2022 09:42:08 +1300)
Sidney Markowitz
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
Sidney Markowitz wrote on 18/12/22 9:42 am:
> 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.
Or an alternative that just came to mind:
Is this perhaps the time for us to switch from svn to git?
We already have the git mirror of svn
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
11 matches
Mail list logo
