Hi all, TL;DR: when Tinc 1.1 release? I plan to use Tinc for my GSoC project which basically simplifies setup of a Tinc mesh providing IPv6 to nodes in community mesh networks. As I'm new to Tinc I don't know it's history and the changes from 1.0 to 1.1, but it seems to have at least a different syntax in some cases. To make and keep it simple for users, I'd like to stick with the upcoming version - which makes me write this mail. Currently OpenWrt snapshots only offer Tinc 1.0, I'd like to create another package like tinc11 (or tinc-ng?) containing the 1.1 release. My question: Are there plans to release Tinc 1.1 any time soon? If not, is there and ETA or what's missing for a release? Thank you very much for all further information! Best, Paul Spooren
Hi Paul, I've been using various 1.1pre versions on Windows, Linux, and Freetz (embedded OS for routers, similar to OpenWRT) for years, and I can't complain. The tinc 1.1 branch is pretty stable and that's where the majority of development happens. Why do you want to wait for an official release? Regards, Daniel -----Original Message----- From: tinc-devel <tinc-devel-bounces at tinc-vpn.org> On Behalf Of Paul Sent: Wednesday, May 16, 2018 8:09 AM To: tinc-devel at tinc-vpn.org Subject: Tinc 1.1 release Hi all, TL;DR: when Tinc 1.1 release? I plan to use Tinc for my GSoC project which basically simplifies setup of a Tinc mesh providing IPv6 to nodes in community mesh networks. As I'm new to Tinc I don't know it's history and the changes from 1.0 to 1.1, but it seems to have at least a different syntax in some cases. To make and keep it simple for users, I'd like to stick with the upcoming version - which makes me write this mail. Currently OpenWrt snapshots only offer Tinc 1.0, I'd like to create another package like tinc11 (or tinc-ng?) containing the 1.1 release. My question: Are there plans to release Tinc 1.1 any time soon? If not, is there and ETA or what's missing for a release? Thank you very much for all further information! Best, Paul Spooren _______________________________________________ tinc-devel mailing list tinc-devel at tinc-vpn.org https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc-devel
Hi Daniel, On Thu, May 17, 2018 at 12:56 AM, Daniel Schall <Daniel-Schall at web.de> wrote:> Hi Paul, > > I've been using various 1.1pre versions on Windows, Linux, and Freetz > (embedded OS for routers, similar to OpenWRT) for years, and I can't > complain. > The tinc 1.1 branch is pretty stable and that's where the majority of > development happens. > Why do you want to wait for an official release?thanks for the quick response! I figured that it's easier to get a Tinc 1.1 release upstream then a pre version. The current maintainer Zioproto stated it's best to have both version separated upstream.>
On Thu, May 17, 2018 at 12:08:43AM +0900, Paul wrote:> TL;DR: when Tinc 1.1 release?When it's ready. I'm sorry, there never has been a schedule for tinc releases. There will be at least two pre-releases; one with the changes that have been accumulating since pre15, then I'll publish a list of changes that need to happen before I'm comfortable with a final version, and make another pre-release when those have been implemented, and then hopefully 1.1.0. A quick overview of things I think need to happen before an 1.1 release: - Remove the python-wxwidgets GUI (it can be re-added in a later release). - Enable AutoConnect by default. - Ensure it tracks address changes of peers. - Fix some SPTPS handshake issues (these are harmless but cause annoying messages and will cause a connection to take longer to form than necessary). - Allow invites with both IPv4 and IPv6 addresses in one invitation URL. - Add a way to easily revoke a node's access to the VPN. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20180605/a3a953ae/attachment.sig>