Bukama commented on code in PR #812: URL: https://github.com/apache/maven-site/pull/812#discussion_r2135254941
########## content/apt/plugins/localization.apt: ########## @@ -125,21 +125,10 @@ Localization of Plugins * Run "mvn site" on that project to test it. - * When you are happy with your translation, create an issue in JIRA for the + * When you are happy with your translation, create a Pull Request for the Review Comment: The page is still about SVN, while the repositories linked are moved to GitHub. ########## content/markdown/issue-management.md: ########## @@ -19,17 +19,17 @@ specific language governing permissions and limitations under the License. --> -Maven projects use [Jira](https://www.atlassian.com/software/jira) as issue tracking and project management application. +Maven projects use GitHub issues as issue tracking and project management application. ## Issue Management Maven is composed of nearly [100 parts](/scm.html#Maven_Sources_Overview), each one having its own Jira project or component: -**see the [Maven Jira issues overview](https://cwiki.apache.org/confluence/display/MAVEN/Maven+JIRA+issues+overview) to get a summary of open issues**. +**see the [Maven Jira issues overview](https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching) to get a summary of open issues**. Issues, bugs, and feature requests should be submitted to the following issue management systems depending on which component is involved: -* Maven "core": <https://issues.apache.org/jira/browse/MNG> +* Maven "core": <https://github.com/apache/maven/issues> Review Comment: Oops I missed that 🤦♂️ ########## content/apt/guides/development/guide-plugin-documentation.apt.vm: ########## @@ -79,8 +79,8 @@ mvn site <project> [...] <issueManagement> - <system>jira</system> - <url>http://jira.someproject.org</url> + <system>github</system> Review Comment: ```suggestion <system>GitHub</system> ``` ########## content/markdown/faq-unoffical.md: ########## @@ -122,7 +122,7 @@ To resolve this error: plug-ins. If the error persists, browse [archived discussions](http://www.mail-archive.com/users@maven.apache.org/), post to the -Maven user list, or log a [ticket](http://jira.codehaus.org/browse/MNG) describing your problem, if you think it is a +Maven user list, or log a [ticket](https://github.com/apache/maven) describing your problem, if you think it is a Review Comment: ```suggestion Maven user list, or log a [ticket](https://github.com/apache/maven/issues) describing your problem, if you think it is a ``` ########## content/apt/developers/release/maven-project-release-procedure.apt: ########## @@ -130,10 +128,7 @@ Subject: [VOTE] Release Apache Maven XXX Plugin version Y.Z Hi, We solved N issues: -https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=XXXXXX&version=YYYYYYY&styleName=Text - -There are still a couple of issues left in JIRA: -https://issues.apache.org/jira/issues/?jql=project%20%3D%20XXXXXXXXXX%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC +https://github.com/apache/maven-compiler-plugin/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A3.14.1 Review Comment: ```suggestion https://github.com/apache/maven-xxxx/issues?q=is%3Aissue%20state%3Aopen ``` ########## content/apt/developers/retirement-plan-plugins.apt: ########## @@ -100,14 +100,14 @@ I will continue with the steps required to retire this plugin. * Make the final release - [[1]] Create an issue in JIRA with the issue type "Task" and the summary + [[1]] Create an issue in GitHub with the issue type "Task" and the summary "Retire this plugin", and schedule it for the final release. If the plugin - includes a JIRA report in the generated site, you will need to close this + includes a GitHub report in the generated site, you will need to close this Review Comment: @slawekjaranowski Does the issue needs to be closed or "only" the related PR to make in the release notes generated by release-drafter? ########## content/apt/shared/index.apt: ########## @@ -77,7 +77,7 @@ Shared Components *----------------------------------------------------------------------------+--------------+-------------------+------------------+------------------------+---------------------+ | {{{/shared/maven-verifier/} <<<maven-verifier>>>}} | 2.0.0-M1 | 2022-09-22 | Used to run Maven builds as part of tests. | {{{https://gitbox.apache.org/repos/asf/maven-verifier.git}Git}} / {{{https://github.com/apache/maven-verifier/}GitHub}} | {{{https://github.com/apache/maven-verifier/issues}GitHub Issues}} *----------------------------------------------------------------------------+--------------+-------------------+------------------+------------------------+---------------------+ -| {{{/scm/} <<<maven-scm>>>}} | 2.1.0 | 2024-04-11 | Generic API to SCM systems. | {{{https://gitbox.apache.org/repos/asf/maven-scm.git}Git}} / {{{https://github.com/apache/maven-scm/}GitHub}} | {{{https://issues.apache.org/jira/browse/SCM}JIRA}} +| {{{/scm/} <<<maven-scm>>>}} | 2.1.0 | 2024-04-11 | Generic API to SCM systems. | {{{https://gitbox.apache.org/repos/asf/maven-scm.git}Git}} / {{{https://github.com/apache/maven-scm/}GitHub}} | {{{https://github.com/apache/maven-scm/issues}GitHub Issues}} Review Comment: Damn shared page 🤦♂️ ########## content/apt/plugins/index.apt: ########## @@ -127,7 +127,7 @@ Available Plugins *--------------------------------------------------------------+------------+--------------+------------+------------------+------------------------+--------------------+ | {{{/plugins/maven-pmd-plugin/} <<<pmd>>>}} | B+R | 3.26.0 | 2024-10-25 | Generate a PMD/CPD report. | {{{https://gitbox.apache.org/repos/asf/maven-pmd-plugin.git}Git}} / {{{https://github.com/apache/maven-pmd-plugin/}GitHub}} | {{{https://github.com/apache/maven-pmd-plugin/issues}GitHub Issues}} *--------------------------------------------------------------+------------+--------------+------------+------------------+------------------------+--------------------+ -| {{{/plugin-tools/maven-plugin-report-plugin/} <<<plugin-report>>>}} | R | 3.15.1 | 2024-10-22 | Create a plugin documentation for any mojos found in the source tree. | {{{https://gitbox.apache.org/repos/asf/maven-plugin-tools.git}Git}} / {{{https://github.com/apache/maven-plugin-tools/}GitHub}} | {{{https://issues.apache.org/jira/browse/MPLUGIN}Jira MPLUGIN}} +| {{{/plugin-tools/maven-plugin-report-plugin/} <<<plugin-report>>>}} | R | 3.15.1 | 2024-10-22 | Create a plugin documentation for any mojos found in the source tree. | {{{https://gitbox.apache.org/repos/asf/maven-plugin-tools.git}Git}} / {{{https://github.com/apache/maven-plugin-tools/}GitHub}} | {{{https://github.com/apache/maven-plugin-tools/issues}GitHub Issues}} Review Comment: hmm so many link I forgot? :O ########## content/markdown/issue-management.md: ########## @@ -19,17 +19,17 @@ specific language governing permissions and limitations under the License. --> -Maven projects use [Jira](https://www.atlassian.com/software/jira) as issue tracking and project management application. +Maven projects use GitHub issues as issue tracking and project management application. ## Issue Management Maven is composed of nearly [100 parts](/scm.html#Maven_Sources_Overview), each one having its own Jira project or component: -**see the [Maven Jira issues overview](https://cwiki.apache.org/confluence/display/MAVEN/Maven+JIRA+issues+overview) to get a summary of open issues**. +**see the [Maven Jira issues overview](https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching) to get a summary of open issues**. Review Comment: Two things: 1) The confluence page about switching to GH does not list unresolved issues. The list contains ALL issues, including closed ones. 2) The confluence page will never list updated numbers from GitHub. We need to create a new site for this, if we want a summary of unresolved GitHub issues ########## content/apt/guides/development/guide-maven-development.apt: ########## @@ -85,9 +84,7 @@ Developing Maven * Create your branch from <<<master>>>, not from a tag. Otherwise, your patch is outdated the moment you create it and might not be applicable to the development head. - * If this was a new piece of work without a JIRA issue, create a JIRA issue for it now. - - * Name the branch after the issue number; the branch name would start with <<<\<jira-project-id>-<ticket-id\>>>>. + * Name the branch after the issue number; the branch name would start with <<<\-<ticket-id\>>>>. Review Comment: ```suggestion * Name the branch after the issue number; the branch name would start with <<<\<ticket-id\>>>>. ``` ########## content/apt/guides/development/guide-maven-development.apt: ########## @@ -38,8 +38,7 @@ Developing Maven * Finding some work to do - First of all you need something to work on! Issues can be found in - {{{/issue-management.html}several JIRA projects}}. + First of all you need something to work on! Issues can be found on each GitHub repo issues. Review Comment: ```suggestion First of all you need something to work on! Issues can be found on the issue tab of each GitHub repository. ``` ########## content/apt/users/getting-help.apt: ########## @@ -67,39 +67,20 @@ Getting Help If it turns out that there is indeed something wrong with Maven or one of the plugins, you should report it to the issue management system. - Please check the project's documentation, if it is still used JIRA (which requires an account - see below) as its issue management system or if it is already migrated to GitHub issues. + All projects (Apache Maven core, Apache Maven plugins, sub components) have been migrated to use GitHub issues. Review Comment: Would just link the "issue management system" page anbd remove the sentence about JIRA/GitHub completely ########## content/apt/developers/retirement-plan-plugins.apt: ########## @@ -131,10 +131,10 @@ but has moved to the <Organization> <Project> project. making sure that you follow the exceptions mentioned above regarding the site deployment. [[1]] When updating the plugins page, move Maven Foo Plugin to under the - "Retired" heading. Remove the SVN/Github and JIRA/Github Issues links and add + "Retired" heading. Remove the SVN/Github and Github Issues links and add the date of retirement. - [[1]] When updating the version in JIRA, do not add Y.Z+1 and make sure you + [[1]] When updating the version in GitHub, do not add Y.Z+1 and make sure you Review Comment: Milestones? ########## content/apt/developers/retirement-plan-plugins.apt: ########## @@ -149,7 +149,7 @@ but has moved to the <Organization> <Project> project. [[1]] When relevant update summary pages for {{{https://maven.apache.org/plugins/index.html}plugins}} or {{{https://maven.apache.org/shared/index.html}shared components}} - [[1]] Add " (RETIRED)" at the end of the project name in JIRA. This needs to be done by PMC members. + [[1]] Add " (RETIRED)" at the end of the project name in GitHub. This needs to be done by PMC members. Review Comment: The JIRA projects also needs to get retried. We don't do this after issue migrations (see the point @hboutemy pointed out yesterday about Attic ########## content/apt/developers/conventions/git.apt: ########## @@ -42,24 +42,17 @@ Maven Git Convention To contribute to a Maven component that is maintained in git, please follow these steps: - [[1]] create a JIRA for bug or improvement that you wish to work Review Comment: I suggest to keep this point that we want an underlying issue in general esp. for discussion. Otherwise we end up more and more with the situation people open PRs of things, they consider bugs, but which are non etc. ########## content/apt/developers/release/maven-project-release-procedure.apt: ########## @@ -86,9 +86,7 @@ Performing a Maven Project Release * use release-drafter to help prepare release notes - in such case all PRs should a proper label - * copy paste release notes from JIRA - - * put link to release notes in JIRA + * copy paste release notes from GitHub Review Comment: (why not only link them - but this discussion is not part of this PR) -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
