3.x#27
Conversation
Bumps [github.com/containernetworking/plugins](https://github.com/containernetworking/plugins) from 1.8.0 to 1.9.0. - [Release notes](https://github.com/containernetworking/plugins/releases) - [Commits](containernetworking/plugins@v1.8.0...v1.9.0) --- updated-dependencies: - dependency-name: github.com/containernetworking/plugins dependency-version: 1.9.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.42.0 to 0.45.0. - [Commits](golang/crypto@v0.42.0...v0.45.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.45.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/containerd/containerd](https://github.com/containerd/containerd) from 1.7.28 to 1.7.29. - [Release notes](https://github.com/containerd/containerd/releases) - [Changelog](https://github.com/containerd/containerd/blob/main/RELEASES.md) - [Commits](containerd/containerd@v1.7.28...v1.7.29) --- updated-dependencies: - dependency-name: github.com/containerd/containerd dependency-version: 1.7.29 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Andreas Peters <ap@aventer.biz>
rajch
left a comment
rajch
left a comment
There was a problem hiding this comment.
First and foremost, thanks! It feels good to have someone else interested in maintaining weave.
Secondly, I had been considering removing "legacy" backend support for iptables for some time now, like you have done in this PR. But it seems people are still using weave on operating systems that only use that backend - you can see a couple of open issues, and there have been some out-of-band support calls as well.
Let me figure out a way of maybe maintaining two version trees: the 2.8.x series which will continue to use legacy, and the 3.x series which would not. At that point, I will merge this PR. I'm a little occupied just now, so this may take a while - say end of March.
|
Hi Rajch, the PR was actually an accident. I intended to create it in my own master branch. 🤦 I would never open such a large PR without squashing the commits and without any description. But since we are already in contact now, I'd like to take the opportunity. I'd be happy if we could continue maintaining and developing Weave together. At the moment I maintain both the 2.x and the 3.x branches. The 2.x line exactly for the reason you mentioned. For 3.x, I'm also planning to move towards nftables instead of iptables, since Red Hat has already marked iptables What do you think? Would you be interested in maintaining the project together, in a relaxed and low-pressure way? Best, |
|
I would love to maintain Weave together. Let's discuss more once I get back. Thanks, |
2 participants
No description provided.