Update release-notes.xml (#133)

In the 2.0.17 release notes section, I changed "Apache log4net 2.0.16 addresses reported issues" to "Apache log4net 2.0.17 addresses reported issues".
1 file changed
tree: 0a265e97e1ba0dcabaad2cc9ec3cfb07b75efa1c
  1. .github/
  2. doc/
  3. examples/
  4. extensions/
  5. local-tasks/
  6. netstandard/
  7. src/
  8. tests/
  9. .asf.yaml
  10. .gitattributes
  11. .gitignore
  12. .zarro-defaults
  13. appveyer.yml
  14. build-with-docker-for-windows.bat
  15. build.cmd
  16. install-dotnet-core-sdk-1.1.ps1
  17. install-net-framework-sdk-3.5.ps1
  18. Jenkinsfile
  19. KEYS
  20. LICENSE
  21. log4net.build
  22. log4net.include
  23. log4net.shfbproj
  24. log4net.snk
  25. log4net.snk.readme
  26. NOTICE
  27. package-icon.png
  28. package-lock.json
  29. package.json
  30. pom.xml
  31. rat.excludesFile
  32. README.md
  33. STATUS.txt
README.md

Introduction

Apache log4net is a sub project of the Apache Logging Services project. Apache log4net graduated from the Apache Incubator in February 2007. Web site: http://logging.apache.org/log4net

Documentation

For the latest documentation see the log4net web site at: http://logging.apache.org/log4net

Contributing

log4net development happens on the logging dev mailing list, see https://logging.apache.org/log4net/mail-lists.html. Please join the mailing list and discuss bigger changes before working on them.

For bigger changes we must ask you to sign a Contributor License Agreement http://www.apache.org/licenses/#clas.

Github pull requests are one way to contribute, The Apache issue tracker is no longer accepting new issues but is available at https://issues.apache.org/jira/browse/LOG4NET for access to previous issues.

Developing

log4net targets a wide array of .net platforms, including some which are out of support from Microsoft, making it difficult to install relevant SDKs and build for those targets. In particular, older Client Profile .NET Framework targets and dotnet core 1.1 may be installed by using the bundled helper scripts:

These scripts download the relevant installers from Microsoft servers, but you run them at your own risk.

Please see