Re: [Openvpn-devel] OpenVPN 2.2.0 released

[Jan J. K. <ja...@ni...>]

Hi,

I just would like to thank dazo, mattock and all the other developers 
and contributors who have put so much time into creating this release  - 
great job guys!

JJK


David Sommerseth wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 27/04/11 20:48, Samuli Seppänen wrote:
> |
> | Note that we've recently switched to using a different Git repository:
> |
> | <git://openvpn.git.sourceforge.net/gitroot/openvpn/openvpn.git>
>
> Just to follow up this one a little bit with more details.
>
> For me personally, the 2.2 release is a remarkable release for the OpenVPN
> community.  This is probably the release with the most visible patches from
> the community.  If I've counted correctly, there are 23 different patch
> authors in addition to the work of James Yonan.  Over 100 patches have been
> contributed and have been implemented.  So I want to thank all of you who have
> contributed with fixes, new features, documentation and other improvements.
>
> To mark that we now are officially using git as the official source
> repository, all releases and the approved patches will now go into the new
> openvpn.git tree, as announced.  This tree will also have release branches,
> one for each major release, like 2.1, 2.2 and the coming 2.3.  All major and
> minor releases (2.1.x, 2.2.x, etc) are in addition tagged.
>
> For more information about the code repositories, please have a look at our wiki:
> <https://community.openvpn.net/openvpn/wiki/DeveloperDocumentation#Coderepositories>
>
>
> We have for about a year used the openvpn-testing.git tree.  The future of
> this tree will be discussed in the near future.  Right now, this tree will be
> available.  The master branch in this tree and in the openvpn.git tree will be
> kept in sync, and all approved feature branches will be merged into allmerged
> together with the master branch when they are considered stable enough.  Right
> now, it is not much new things in the allmerged branch, as the last
> outstanding and approved feature branches was the IPv6 branches.
>
> As you now understand, the OpenVPN 2.3 will have IPv6 as one of the more
> important features.  Both feat_ipv6_transport (connecting/listening to IPv6
> addresses between OpenVPN client and server) and feat_ipv6_payload
> (transporting IPv6 traffic inside the tunnel) have been available in the
> allmerged branch for about a year, so it is considered safe and stable enough
> to be merged into the master branch.  So everyone who wants to begin to look
> at what OpenVPN 2.3 really will bring, grab the a master branch.
>
>
> So to summarise it quickly:  openvpn.git is the main git repository, where all
> that has been released and will be released in the coming OpenVPN releases can
> be found.  The openvpn-testing.git repository contains now experimental code
> which needs a lot of testing and possibly much more development.  And the
> master branch in both trees will stay in sync.  What is in found the master
> branch will make it into a coming release.
>
> Again thanks to all support and contributions.  They are indeed very much
> appreciated!
>