Hi,

We at the OpenVPN project are going to start distributing our Windows installers using Chocolatey. The goal is to allow easy upgrades for users, as well as for our CI systems. The details are not set yet, so I'm contacting you before moving forward. For Debian/Ubuntu we have a fairly wide range of repositories (source):

• stable: stable releases only - no alphas, betas or RCs
• testing: latest releases, including alphas/betas/RCs
• release/2.3: OpenvPN 2.3 releases
• release/2.4: OpenVPN 2.4 releases, including alphas/betas/RCs

For Windows we're planning on having two repositories initially:

• stable: stable releases only - no alphas, betas or RCs
• snapshots: packages based on latest Git "master" code

It looks like your release strategy on chocolatey.org is very close to stable, and I don't think it makes sense for the OpenVPN project to create its own repository where it would distribute an openvpn package which is essentially identical to what you distribute on chocolatey.org.

So, would you be willing to co-operate with us on the stable OpenVPN Windows releases? Besides working together on code in this repository, I would like to see new, stable OpenVPN versions getting into chocolatey.org on the release day (if possible).

Thoughts?