On 5/21/09, Felix Kronlage <f...@perrin.bytemine.net> wrote: > On Wed, May 20, 2009 at 11:39:57AM +0200, Matthias Andree wrote: > > > + release openvpn 2.1 without Windows GUI as soon as you believe it's done > > * your changelog below suggests that RC16 needs more than just > > a week of testing > > + stabilize (through beta and RC) the Windows GUI as a separate add-on > > package (if you want, these test releases can then comprise 2.1_rc, > > 2.1.0, 2.1.1, ... whichever is current, for user convenience) > > > ack. > Small and fast release cycles. At least 'fast' compared to now would > be nice.
Yes... OpenVPN has several separate components, each can be released separately: 1. OpenVPN core (Source). 2. OpenVPN easy-rsa (Source) 3. OpenVPN binaries (Whoever use this, Windows is important). 4. OpenVPN TAP device (Windows only, device driver). 5. OpenVPN UI (Windows only, binary?) 6. OpenVPN Windows Installer (Installer + OpenVPN Windows binaries + easy-rsa + Tap + UI) It would be much easier if every component has its own version and dependency. For example OpenVPN-2.1 requires >=TAP-1.0.5 on target machine. OpenVPN-2.1-win32-build-22 is build 22 out of OpenVPN-2.1 sources. OpenVPN-2.1-installer-23-x86 - is installer version 23 for x86 which is a bundle of OpenVPN-2.1-win32-build22, easy-rsa-2.0.2, tap-1.0.5, UI-2.2.2 etc... Alon.
