On 28/03/17 14:41, Steffan Karger wrote:
> On 28-03-17 15:31, Samuli Seppänen wrote:
>> On 28/03/2017 16:08, Steffan Karger wrote:
>>> On 28-03-17 15:02, debbie10t wrote:
>>>> On 28/03/17 13:47, Gert Doering wrote:
>>>>> We need to communicate better what might affect users in new versions, so
>>>>> they can test and complain/adjust in time (like, the stricter CRL handling
>>>>> in 2.4, and - obviously - the --tls-remote bit)
>>>>
>>>> Suggestion: A Wiki Page detailing deprecation plans with dated targets.
>>>
>>> We have Changes.rst for that:
>>> https://github.com/OpenVPN/openvpn/blob/master/Changes.rst
>>>
>>> Let's please keep this list on one location only, and I think
>>> Changes.rst is the right place.
>>
>> Ah, Changes.rst had "Deprecated features" section, good. I think that is
>> sufficient. The question then becomes: do we need to link to Changes.rst
>> from somewhere so that people find it?
>>
>
> Yeah, linking to the changes.rst on github (which gets nicely rendered)
> from the wiki sounds like a good plan.

Agreed: a simple Deprecation page on the wiki linking to changes.rst

The wiki page *could* also be updated from time to time to provide
specific warnings of important changes like deprecating --ns-cert-type
as it has been identified that it will likely effect many people.

I would be happy to help maintain such warnings as they are mentioned
the devel mailing list.

Regards


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to