> Generally speaking, I'd prefer as few changes to the 2.3 branch as > possible. Try to let it be bugfixes mostly. This is also to encourage > users to move over to 2.4 ASAP when that's ready, with more new > features. It also helps stability and maintainability within the > OpenVPN project. > > Arne's OpenVPN for Android seems to always have been more experimental > and bleeding edge than OpenVPN Connect. So unless Arne screams back at > me telling me I'm wrong, I believe Arne will be one of the first ones to > move over to the 2.4/master codebase, thus not making things that > difficult for him. But Arne is the one who can fully answer this. If > he says it will be more complicated, then let it go into 2.3 too. I am already on 2.4/master codebase. I might consider tracking release/2.4 in the future but definitively not release/2.3. (With all the bugfixes/patches I need/want on Android it would be almost -master anyway).
I have not really an opinoion about 2.3 and what should go in there. At the moment it feels like release/2.3 is a "baby" master since almost all changes are cherry picked into it. Arne
signature.asc
Description: OpenPGP digital signature
