You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shiro.apache.org by "GaneshPatil7517 (via GitHub)" <gi...@apache.org> on 2026/01/30 13:42:52 UTC

[PR] This PR updates the documentation to reflect the use of GitHub Issues and GitHub Discussions, and marks JIRA as legacy for archival purposes only. Resolves #281. [shiro-site]

GaneshPatil7517 opened a new pull request, #282:
URL: https://github.com/apache/shiro-site/pull/282

   This PR updates the documentation to reflect the use of GitHub Issues and GitHub Discussions, and marks JIRA as legacy for archival purposes only.
   
   ### Changes
   
   - **issues.adoc**: Updated to use GitHub Issues as the primary tracker, added GitHub Discussions for questions, and added a JIRA (Legacy) section
   - **support.adoc**: Added GitHub Discussions and GitHub Issues at the top of the support resources
   - **community.adoc**: Replaced generic "Issue Tracker" with separate GitHub Discussions and GitHub Issues entries
   - **forums.adoc**: Added GitHub Discussions section for community questions
   - **mailing-lists.adoc**: Renamed "Shiro Issues/JIRA List" to "Shiro Issues List"
   
   Resolves #281.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@shiro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] This PR updates the documentation to reflect the use of GitHub Issues and GitHub Discussions, and marks JIRA as legacy for archival purposes only. Resolves #281. [shiro-site]

Posted by "Copilot (via GitHub)" <gi...@apache.org>.

Copilot commented on code in PR #282:
URL: https://github.com/apache/shiro-site/pull/282#discussion_r2747339625


##########
src/site/content/forums.adoc:
##########
@@ -6,7 +6,18 @@
 :jbake-description: Access Apache Shiro community forums and mailing list archives via ASF Pony Mail for user and developer discussions.
 :idprefix:
 
-For users that prefer to use browse the mailing lists with a browser can use https://lists.apache.org/[ASF Lists] (Pony Mail).
+== Mailing Lists
+
+For those that may prefer mailing lists, please see the link:mailing-lists.html[Mailing Lists] information.
+____
+
+*NOTE:* The primary forums for Apache Shiro are the mailing lists, which can be accessed via the link:mailing-lists.html[Mailing Lists] page. This is per the Apache Software Foundation's community guidelines.
+
+____

Review Comment:
   The NOTE callout is currently written as bold text inside an open block (____). In AsciiDoc, this won't render as an admonition; prefer using a proper NOTE admonition (e.g., "NOTE: ..." or a [NOTE] block) and drop the open block unless it is needed for formatting.



##########
src/site/content/issues.adoc:
##########
@@ -3,24 +3,32 @@
 :jbake-type: page
 :jbake-status: published
 :jbake-tags: issues, bugs, jira, bug-tracking, support
-:jbake-description: Report bugs, request features, and track issues for Apache Shiro using Atlassian Jira issue tracking system.
+:jbake-description: Report bugs, request features, and track issues for Apache Shiro using GitHub Issues tracking system.
 :idprefix:
 :icons: font
 
-Apache Shiro uses Atlassian Jira for tracking tasks, feature requests, bugs, and other issues related to the project development.
+Apache Shiro uses https://github.com/apache/shiro/issues[GitHub Issues] for bug reports, feature requests, and task tracking.
+
+For questions, ideas, and community discussions, please use https://github.com/apache/shiro/discussions[GitHub Discussions].
 
 == Usage Guidelines
 
-Jira is provided as a Shiro software development resource.
-It is meant to be for managing bugs, tasks and improvements in the software itself - it is not a support portal to ask for advice or help.
-For community advice and help in using Apache Shiro, please visit the link:/support.html[Support] page.
+GitHub Issues is provided as a Shiro software development resource.
+It is meant for reporting bugs, requesting features, and tracking improvements in the software itself - it is not a support portal to ask for advice or help.
+For community advice and help in using Apache Shiro, please visit the link:/support.html[Support] page or use https://github.com/apache/shiro/discussions[GitHub Discussions].

Review Comment:
   PR description says support.adoc was updated to add GitHub Discussions/Issues at the top of support resources, but support.adoc currently has no GitHub Discussions/Issues entries. Either update support.adoc accordingly or adjust the PR description to match the actual changes.



##########
src/site/content/issues.adoc:
##########
@@ -3,24 +3,32 @@
 :jbake-type: page
 :jbake-status: published
 :jbake-tags: issues, bugs, jira, bug-tracking, support
-:jbake-description: Report bugs, request features, and track issues for Apache Shiro using Atlassian Jira issue tracking system.
+:jbake-description: Report bugs, request features, and track issues for Apache Shiro using GitHub Issues tracking system.

Review Comment:
   The jbake description reads "using GitHub Issues tracking system", which is grammatically awkward. Consider rephrasing to "using GitHub Issues" or "using the GitHub Issues issue-tracking system".
   ```suggestion
   :jbake-description: Report bugs, request features, and track issues for Apache Shiro using GitHub Issues.
   ```



##########
src/site/content/community.adoc:
##########
@@ -30,6 +30,8 @@ At the Shiro project we make it easy for anyone to join our great community and
 
 * *link:developer-resources.html[Developer Resources]* - Helpful information for anyone providing project help as a committer or contributor
 
-* *https://github.com/apache/shiro/issues[Issue Tracker]* - Once you're ready to contribute, this is a good place to see what needs to get done
+* *https://github.com/apache/shiro/discussions[GitHub Discussions]* - For questions, ideas, and community discussion
+
+* *https://github.com/apache/shiro/issues[GitHub Issues]* - For bug reports and feature requests

Review Comment:
   After adding GitHub Discussions/Issues links here, the earlier bullet in this file that says the project "use[s] Nabble" for forums is now inconsistent with the updated forums page (and the note that Nabble no longer hosts archives). Please update/remove the Nabble wording to match the current support channels.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@shiro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] This PR updates the documentation to reflect the use of GitHub Issues and GitHub Discussions, and marks JIRA as legacy for archival purposes only. Resolves #281. [shiro-site]

Posted by "Copilot (via GitHub)" <gi...@apache.org>.

Copilot commented on code in PR #282:
URL: https://github.com/apache/shiro-site/pull/282#discussion_r2746379012


##########
src/site/content/issues.adoc:
##########
@@ -7,20 +7,28 @@
 :idprefix:
 :icons: font
 
-Apache Shiro uses Atlassian Jira for tracking tasks, feature requests, bugs, and other issues related to the project development.
+Apache Shiro uses https://github.com/apache/shiro/issues[GitHub Issues] for bug reports, feature requests, and task tracking.
+
+For questions, ideas, and community discussions, please use https://github.com/apache/shiro/discussions[GitHub Discussions].

Review Comment:
   The page metadata still says it uses Atlassian Jira (":jbake-description: ... using Atlassian Jira issue tracking system."), but the content now points users to GitHub Issues/Discussions. Please update the jbake description (and any other metadata on this page that mentions Jira as current) so SEO/page summaries aren’t misleading.



##########
src/site/content/support.adoc:
##########
@@ -10,8 +10,9 @@ The Shiro project offers support through its community of users, contributors, a
 
 We encourage everyone to participate and use the available community support tools below.
 
+* https://github.com/apache/shiro/discussions[GitHub Discussions] - For questions, ideas, and community discussion
+* https://github.com/apache/shiro/issues[GitHub Issues] - For bug reports and feature requests
 * link:troubleshooting.html[Troubleshooting & FAQ]
 * link:mailing-lists.html[Mailing Lists]
 * link:forums.html[Forums]
-* link:issues.html[Issues and Bug Tracking]
 * link:commercial-support.html[Commercial Support]

Review Comment:
   This change removes the link to the local `issues.html` page from the Support resources list. Since `issues.adoc` still exists and contains usage guidelines (and the new JIRA legacy notes), consider keeping an internal link to `issues.html` here (in addition to the direct GitHub links), or confirm that the page is discoverable elsewhere in the site navigation.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@shiro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] This PR updates the documentation to reflect the use of GitHub Issues and GitHub Discussions, and marks JIRA as legacy for archival purposes only. Resolves #281. [shiro-site]

Posted by "lprimak (via GitHub)" <gi...@apache.org>.

lprimak merged PR #282:
URL: https://github.com/apache/shiro-site/pull/282


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@shiro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org