On 13/01/17 10:05, Samuli Seppänen wrote: > Il 13/01/2017 10:50, Ilya Shipitsin ha scritto: >> --- >> .github/PULL_REQUEST_TEMPLATE.md | 8 ++++++++ >> 1 file changed, 8 insertions(+) >> create mode 100644 .github/PULL_REQUEST_TEMPLATE.md >> >> diff --git a/.github/PULL_REQUEST_TEMPLATE.md >> b/.github/PULL_REQUEST_TEMPLATE.md >> new file mode 100644 >> index 0000000..d0cfd7f >> --- /dev/null >> +++ b/.github/PULL_REQUEST_TEMPLATE.md >> @@ -0,0 +1,8 @@ >> +# Thank you for your contribution >> + >> +You are welcome to open PR, but they are used for discussion only. All >> +patches must eventually go to the openvpn-devel mailing list for review. >> +For details, see these Wiki articles: >> + >> +* https://community.openvpn.net/openvpn/wiki/Contributing >> +* https://community.openvpn.net/openvpn/wiki/DeveloperDocumentation >> > > Based on testing in the travis-openssl-test repository the template > works as intended, so ACK on that part. > > Any comments on the text itself?
How does this work with branches? Do we need to say that new patches should go into the master branch primarily, unless it is fixing a bug or another issue which is only relevant for specific release branches? -- kind regards, David Sommerseth OpenVPN Technologies, Inc
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
