You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by ma...@apache.org on 2023/01/22 22:26:29 UTC

[logging-log4j-kotlin] branch master updated: Update links to issue tracker

This is an automated email from the ASF dual-hosted git repository.

mattsicker pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4j-kotlin.git


The following commit(s) were added to refs/heads/master by this push:
     new ffd7406  Update links to issue tracker
ffd7406 is described below

commit ffd7406dbac7170afb7409bffb86a3f621afbdc0
Author: Matt Sicker <ma...@apache.org>
AuthorDate: Sun Jan 22 16:26:15 2023 -0600

    Update links to issue tracker
---
 CONTRIBUTING.md | 7 +++----
 NOTICE.txt      | 2 +-
 README.md       | 7 +++----
 3 files changed, 7 insertions(+), 9 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 11af93b..0713e59 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -26,7 +26,7 @@ follow so that we can have a chance of keeping on top of things.
 
 + Make sure you have a [GitHub account](https://github.com/join).
 + If you're planning to implement a new feature it makes sense to discuss your changes on the [dev list](https://logging.apache.org/log4j/2.x/mail-lists.html) first. This way you can make sure you're not wasting your time on something that isn't considered to be in Apache Log4j's scope.
-+ Submit a ticket for your issue, assuming one does not already exist.
++ [Submit a ticket](https://github.com/apache/logging-log4j-kotlin/issues) for your issue, assuming one does not already exist.
   + Clearly describe the issue including steps to reproduce when it is a bug.
   + Make sure you fill in the earliest version that you know has the issue.
 + Fork the repository on GitHub.
@@ -58,10 +58,9 @@ In this case, it is appropriate to start the first line of a commit with '(doc)'
 ## Additional Resources
 
 + [Project Guidelines](https://logging.apache.org/log4j/2.x/guidelines.html)
-+ [Code Style Guide](https://logging.apache.org/log4j/2.x/javastyle.html)
-+ [Apache Log4j 2 Issue Tracker](https://github.com/apache/logging-log4j2/issues)
++ [Apache Log4j API for Kotlin Issue Tracker](https://github.com/apache/logging-log4j-kotlin/issues)
 + [Contributor License Agreement][cla]
 + [General GitHub documentation](https://docs.github.com/)
 + [GitHub pull request documentation](https://docs.github.com/en/pull-requests)
 
-[cla]:https://www.apache.org/licenses/#clas
\ No newline at end of file
+[cla]:https://www.apache.org/licenses/#clas
diff --git a/NOTICE.txt b/NOTICE.txt
index af62f1f..1129ca4 100644
--- a/NOTICE.txt
+++ b/NOTICE.txt
@@ -1,5 +1,5 @@
 Apache Log4j
-Copyright 2021 Apache Software Foundation
+Copyright 2021-2023 Apache Software Foundation
 
 This product includes software developed at
 The Apache Software Foundation (http://www.apache.org/).
diff --git a/README.md b/README.md
index f0405b2..0fe7c6e 100644
--- a/README.md
+++ b/README.md
@@ -95,11 +95,10 @@ see [Snapshot builds](https://logging.apache.org/log4j/2.x/maven-artifacts.html#
 
 ## Issue Tracking
 
-Issues, bugs, and feature requests should be submitted to the 
-[JIRA issue tracking system for this project](https://issues.apache.org/jira/browse/LOG4J2).
+Issues, bugs, and feature requests should be submitted to the
+[GitHub issues page for this project](https://github.com/apache/logging-log4j-kotlin/issues).
 
-Pull request on GitHub are welcome, but please open a ticket in the JIRA issue tracker first, and mention the 
-JIRA issue in the Pull Request.
+Pull request on GitHub are welcome; corresponding GitHub issues should be referenced in the PR.
 
 ## Building From Source