[INLONG-4727][Doc] Update InLong project link in readme and pom.xml (#…

…4729)

Co-authored-by: Yuanhao Ji <[email protected]>

.github/ISSUE_TEMPLATE/config.yml

@@ -18,5 +18,5 @@
 blank_issues_enabled: false
 contact_links:
   - name: '❓ Question'
-    url: https://github.com/apache/incubator-inlong/discussions
+    url: https://github.com/apache/inlong/discussions
     about: Ask a question or request support for using Apache InLong

.github/PULL_REQUEST_TEMPLATE.md

@@ -3,7 +3,7 @@
 
 - Title Example: [INLONG-XYZ][Component] Title of the pull request
 
-*(The following *XYZ* should be replaced by the actual [GitHub Issue](https://github.com/apache/incubator-inlong/issues) number)*
+*(The following *XYZ* should be replaced by the actual [GitHub Issue](https://github.com/apache/inlong/issues) number)*
 
 - Fixes #XYZ
 

.github/ct.yml

@@ -18,3 +18,4 @@
 chart-dirs:
   - 'docker'
 validate-maintainers: true
+check-version-increment: false

.github/workflows/README.md

@@ -2,25 +2,25 @@
 
 This directory contains all InLong CI checks.
 
-- [![InLong Build](https://github.com/apache/incubator-inlong/actions/workflows/ci_build.yml/badge.svg)](https://github.com/apache/incubator-inlong/actions/workflows/ci_build.yml)
+- [![InLong Build](https://github.com/apache/inlong/actions/workflows/ci_build.yml/badge.svg)](https://github.com/apache/inlong/actions/workflows/ci_build.yml)
 
   Build InLong when pushing changes or opening a pull request.
 
   If it passes, you can download the InLong binary package from the workflow run's URL.
 
-- [![InLong Unit Test](https://github.com/apache/incubator-inlong/actions/workflows/ci_ut.yml/badge.svg)](https://github.com/apache/incubator-inlong/actions/workflows/ci_ut.yml)
+- [![InLong Unit Test](https://github.com/apache/inlong/actions/workflows/ci_ut.yml/badge.svg)](https://github.com/apache/inlong/actions/workflows/ci_ut.yml)
 
   Unit testing when pushing changes or opening a pull request.
 
   If it fails, you can check out reports form the workflow run's URL.
 
-- [![InLong Docker Build and Push](https://github.com/apache/incubator-inlong/actions/workflows/ci_docker.yml/badge.svg)](https://github.com/apache/incubator-inlong/actions/workflows/ci_docker.yml)
+- [![InLong Docker Build and Push](https://github.com/apache/inlong/actions/workflows/ci_docker.yml/badge.svg)](https://github.com/apache/inlong/actions/workflows/ci_docker.yml)
 
   Build Docker images when pushing changes or opening a pull request.
 
-  Only when pushing changes to the `apache/incubator-inlong` repository will the Docker images are pushed to [Docker Hub](https://hub.docker.com/u/inlong).
+  Only when pushing changes to the `apache/inlong` repository will the Docker images are pushed to [Docker Hub](https://hub.docker.com/u/inlong).
 
-- [![InLong Helm Charts Lint and Test](https://github.com/apache/incubator-inlong/actions/workflows/ci_chart_test.yml/badge.svg)](https://github.com/apache/incubator-inlong/actions/workflows/ci_chart_test.yml)
+- [![InLong Helm Charts Lint and Test](https://github.com/apache/inlong/actions/workflows/ci_chart_test.yml/badge.svg)](https://github.com/apache/inlong/actions/workflows/ci_chart_test.yml)
 
   Lint and test the InLong Helm Chart when pushing changes or opening a pull request.
 
@@ -32,37 +32,37 @@ This directory contains all InLong CI checks.
 
   > NOTE: If the charts have not changed, they will not be linted, validated, installed and tested.
 
-- [![InLong Check License Header](https://github.com/apache/incubator-inlong/actions/workflows/ci_check_license.yml/badge.svg)](https://github.com/apache/incubator-inlong/actions/workflows/ci_check_license.yml)
+- [![InLong Check License Header](https://github.com/apache/inlong/actions/workflows/ci_check_license.yml/badge.svg)](https://github.com/apache/inlong/actions/workflows/ci_check_license.yml)
 
   Check licence header when pushing changes or opening a pull request using the [apache/skywalking-eyes](https://github.com/apache/skywalking-eyes) action.
   And here is the [configuration](../../.licenserc.yaml).
 
-- [![InLong Pull Request Labeler](https://github.com/apache/incubator-inlong/actions/workflows/ci_labeler.yml/badge.svg)](https://github.com/apache/incubator-inlong/actions/workflows/ci_labeler.yml)
+- [![InLong Pull Request Labeler](https://github.com/apache/inlong/actions/workflows/ci_labeler.yml/badge.svg)](https://github.com/apache/inlong/actions/workflows/ci_labeler.yml)
 
   label new pull requests based on the paths of files being changed using the [actions/labeler](https://github.com/actions/labeler) action.
   And here is the [labeler configuration](../labeler.yml)
 
-- [![InLong Mark Stale Issues and PRs](https://github.com/apache/incubator-inlong/actions/workflows/ci_stale.yml/badge.svg)](https://github.com/apache/incubator-inlong/actions/workflows/ci_stale.yml)
+- [![InLong Mark Stale Issues and PRs](https://github.com/apache/inlong/actions/workflows/ci_stale.yml/badge.svg)](https://github.com/apache/inlong/actions/workflows/ci_stale.yml)
 
   Mark issues and pull requests that have not had recent interaction using the [actions/stale](https://github.com/actions/stale) action.
 
-- [![InLong Greeting](https://github.com/apache/incubator-inlong/actions/workflows/ci_greeting.yml/badge.svg)](https://github.com/apache/incubator-inlong/actions/workflows/ci_greeting.yml)
+- [![InLong Greeting](https://github.com/apache/inlong/actions/workflows/ci_greeting.yml/badge.svg)](https://github.com/apache/inlong/actions/workflows/ci_greeting.yml)
 
   Interact with newcomers using the [actions/first-interaction](https://github.com/actions/first-interaction) action.
 
-- [![InLong Check Pull Request Title](https://github.com/apache/incubator-inlong/actions/workflows/ci_check_pr_title.yml/badge.svg)](https://github.com/apache/incubator-inlong/actions/workflows/ci_check_pr_title.yml)
+- [![InLong Check Pull Request Title](https://github.com/apache/inlong/actions/workflows/ci_check_pr_title.yml/badge.svg)](https://github.com/apache/inlong/actions/workflows/ci_check_pr_title.yml)
 
   Check pull request title.
 
   Title Example: `[INLONG-XYZ][Component] Title of the pull request`
 
-  > - **XYZ** should be replaced by the actual [GitHub Issue](https://github.com/apache/incubator-inlong/issues) number, e.g. `[INLONG-123]`
+  > - **XYZ** should be replaced by the actual [GitHub Issue](https://github.com/apache/inlong/issues) number, e.g. `[INLONG-123]`
   >
   > - **Component** should be replaced by the InLong component name, e.g. `[INLONG-123][Manager]`
 
 ### Troubleshooting
 
-If you have any questions, welcome to contact the maintainers. And feel free to make a [pull request](https://github.com/apache/incubator-inlong/compare)!
+If you have any questions, welcome to contact the maintainers. And feel free to make a [pull request](https://github.com/apache/inlong/compare)!
 
 ### Maintainers
 

.github/workflows/ci_check_pr_title.yml

@@ -47,7 +47,7 @@ jobs:
             # add a job summary
             echo "## This pull request title is not valid! :bug:" >> $GITHUB_STEP_SUMMARY
             echo "Title Example: \`[INLONG-XYZ][Component] Title of the pull request\`" >> $GITHUB_STEP_SUMMARY
-            echo "> - **XYZ** should be replaced by the actual [GitHub Issue](https://github.com/apache/incubator-inlong/issues) number, e.g. \`[INLONG-123]\`" >> $GITHUB_STEP_SUMMARY
+            echo "> - **XYZ** should be replaced by the actual [GitHub Issue](https://github.com/apache/inlong/issues) number, e.g. \`[INLONG-123]\`" >> $GITHUB_STEP_SUMMARY
             echo "> - **Component** should be replaced by the InLong component name, e.g. \`[INLONG-123][Manager]\`" >> $GITHUB_STEP_SUMMARY
 
             exit 1

CONTRIBUTING.md

@@ -19,7 +19,7 @@
 
 -->
 
-## Contributing to Apache InLong(incubating)
+## Contributing to Apache InLong
 
 We would love for you to contribute to Apache InLong and make it even better!
 Please check the [Contribution Guide for Apache InLong](https://inlong.apache.org/community/how-to-contribute)

README.md

@@ -21,8 +21,8 @@
 
 
 # Apache InLong
-[![Build Status](https://travis-ci.org/apache/incubator-inlong.svg?branch=master)](https://github.com/apache/incubator-inlong/actions)
-[![CodeCov](https://codecov.io/gh/apache/incubator-inlong/branch/master/graph/badge.svg)](https://codecov.io/gh/apache/incubator-inlong)
+[![Build Status](https://travis-ci.org/apache/inlong.svg?branch=master)](https://github.com/apache/inlong/actions)
+[![CodeCov](https://codecov.io/gh/apache/inlong/branch/master/graph/badge.svg)](https://codecov.io/gh/apache/inlong)
 [![Maven Central](https://maven-badges.herokuapp.com/maven-central/org.apache.inlong/inlong/badge.svg)](http://search.maven.org/#search%7Cga%7C1%7Corg.apache.inlong)
 [![GitHub release](https://img.shields.io/badge/release-download-orange.svg)](https://inlong.apache.org/download/main)
 [![License](https://img.shields.io/badge/license-Apache%202-4EB1BA.svg)](https://www.apache.org/licenses/LICENSE-2.0.html)
@@ -39,14 +39,14 @@
 - [License](#license)
 
 # What is Apache InLong?
-[Apache InLong](https://inlong.apache.org)(incubating) is a one-stop integration framework for massive data that provides automatic, secure and reliable data transmission capabilities. InLong supports both batch and stream data processing at the same time, which offers great power to build data analysis, modeling and other real-time  applications based on streaming data.
+[Apache InLong](https://inlong.apache.org) is a one-stop integration framework for massive data that provides automatic, secure and reliable data transmission capabilities. InLong supports both batch and stream data processing at the same time, which offers great power to build data analysis, modeling and other real-time  applications based on streaming data.
 
 InLong (应龙) is a divine beast in Chinese mythology who guides the river into the sea, and it is regarded as a metaphor of the InLong system for reporting data streams.
 
 InLong was originally built at Tencent, which has served online businesses for more than 8 years, to support massive data (data scale of more than 80 trillion pieces of data per day) reporting services in big data scenarios. The entire platform has integrated 5 modules:  Ingestion, Convergence, Caching, Sorting, and Management, so that the business only needs to provide data sources, data service quality, data landing clusters and data landing formats, that is, the data can be continuously pushed from the source to the target cluster, which greatly meets the data reporting service requirements in the business big data scenario.
 
 For getting more information, please visit our project documentation at https://inlong.apache.org/
-<img src="https://github.com/apache/incubator-inlong-website/blob/master/static/img/inlong-structure-en.png" align="center" alt="Apache InLong"/>
+<img src="https://github.com/apache/inlong-website/blob/master/static/img/inlong-structure-en.png" align="center" alt="Apache InLong"/>
 
 
 ## Features
@@ -125,7 +125,7 @@ after compile successfully, you could find distribution file at `inlong-distribu
 - [Dashboard Plugin extends a Data Node page](https://inlong.apache.org/docs/next/design_and_concept/how_to_write_plugin_dashboard)
 
 ## Contribute to InLong
-- Report any issue on [GitHub Issue](https://github.com/apache/incubator-inlong/issues)
+- Report any issue on [GitHub Issue](https://github.com/apache/inlong/issues)
 - Code pull request according to [How to contribute](https://inlong.apache.org/community/how-to-contribute).
 
 ## Contact Us
@@ -137,7 +137,7 @@ after compile successfully, you could find distribution file at `inlong-distribu
 
 ## Documentation
 - Home page: https://inlong.apache.org/
-- Issues: https://github.com/apache/incubator-inlong/issues
+- Issues: https://github.com/apache/inlong/issues
 
 ## License
 © Contributors Licensed under an [Apache-2.0](LICENSE) license.

docker/kubernetes/Chart.yaml

@@ -22,7 +22,7 @@ description: A Helm Chart for Apache InLong
 home: https://inlong.apache.org
 icon: https://inlong.apache.org/img/first-page-bg.png
 sources:
-  - https://github.com/apache/incubator-inlong
+  - https://github.com/apache/inlong
 keywords:
   - inlong
   - tubemq

docker/kubernetes/README.md

@@ -228,13 +228,13 @@ When you decide to contribute, you should follow these steps:
 
 1. Develop the chart locally and verify your changes.
 2. Don't forget to bump up the version in [Chart.yaml](Chart.yaml).
-3. Feel free to make a [Pull Request](https://github.com/apache/incubator-inlong/compare)!
-4. Finally, you can view the status of the [lint and test workflow](https://github.com/apache/incubator-inlong/actions/workflows/ci_chart_test.yml).
+3. Feel free to make a [Pull Request](https://github.com/apache/inlong/compare)!
+4. Finally, you can view the status of the [lint and test workflow](https://github.com/apache/inlong/actions/workflows/ci_chart_test.yml).
    > In this workflow, changes between your branch and the master branch will be checked and listed.
    > All changed charts will be linted, validated, installed and tested.
 
 ## Troubleshooting
 
 We've done our best to make these charts as seamless as possible, but occasionally there are circumstances beyond our control.
 We've collected tips and tricks for troubleshooting common issues.
-Please examine these first before raising an [issue](https://github.com/apache/incubator-inlong/issues/new/choose), and feel free to make a [Pull Request](https://github.com/apache/incubator-inlong/compare)!
+Please examine these first before raising an [issue](https://github.com/apache/inlong/issues/new/choose), and feel free to make a [Pull Request](https://github.com/apache/inlong/compare)!

inlong-dashboard/README.md

@@ -1,5 +1,5 @@
 ## About Dashboard
-This is a dashboard console for us to use the [Apache InLong incubator](https://github.com/apache/incubator-inlong).
+This is a dashboard console for us to use the [Apache InLong](https://github.com/apache/inlong).
 
 ## Build
 

inlong-tubemq/pom.xml

@@ -41,15 +41,15 @@
     </licenses>
 
     <scm>
-        <connection>scm:git:[email protected]:apache/incubator-inlong.git</connection>
-        <developerConnection>scm:git:https://gitbox.apache.org/repos/asf/incubator-inlong.git</developerConnection>
-        <url>scm:git:[email protected]:apache/incubator-inlong.git</url>
+        <connection>scm:git:[email protected]:apache/inlong.git</connection>
+        <developerConnection>scm:git:https://gitbox.apache.org/repos/asf/inlong.git</developerConnection>
+        <url>scm:git:[email protected]:apache/inlong.git</url>
         <tag>HEAD</tag>
     </scm>
 
     <issueManagement>
         <system>GitHub Issue</system>
-        <url>https://github.com/apache/incubator-inlong/issues</url>
+        <url>https://github.com/apache/inlong/issues</url>
     </issueManagement>
 
     <mailingLists>

inlong-tubemq/tubemq-client-twins/tubemq-client-cpp/README.md

@@ -39,4 +39,4 @@
 
 
 ## (Optional) build using docker
-  * [build c++ sdk](https://github.com/apache/incubator-tubemq/tree/master/tubemq-docker/tubemq-cpp)
+  * [build c++ sdk](https://github.com/apache/inlong/tree/master/inlong-tubemq/tubemq-docker/tubemq-cpp)

inlong-tubemq/tubemq-client-twins/tubemq-client-cpp/proto/readme.md

@@ -15,6 +15,6 @@
  * limitations under the License.
  */
 
-The proto directory and files are copied from https://github.com/apache/incubator-tubemq/tree/master/tubemq-core/src/main/proto
+The proto directory and files are copied from https://github.com/apache/inlong/tree/master/inlong-tubemq/tubemq-core/src/main/proto
 
 Corresponding *.cc and *.h files are compiled with protobuf 2.5.0 version, if you need other protobuf version's source code, please directly compile *.proto file.

inlong-tubemq/tubemq-client-twins/tubemq-client-go/README.md

@@ -18,14 +18,14 @@
     under the License.
 
 -->
-[![Go Report Card](https://goreportcard.com/badge/github.com/apache/incubator-inlong)](https://goreportcard.com/report/github.com/apache/incubator-inlong)
+[![Go Report Card](https://goreportcard.com/badge/github.com/apache/inlong)](https://goreportcard.com/report/github.com/apache/inlong)
 [![Language](https://img.shields.io/badge/Language-Go-blue.svg)](https://golang.org/)
 # TubeMQ Go Client Library
 
 ## Goal
 
 This project is a pure-Go client library for TubeMQ that does not
-depend on the [TubeMQ C++ library](https://github.com/apache/incubator-inlong/tree/master/inlong-tubemq/tubemq-client-twins/tubemq-client-cpp). Production is not supported yet.
+depend on the [TubeMQ C++ library](https://github.com/apache/inlong/tree/master/inlong-tubemq/tubemq-client-twins/tubemq-client-cpp). Production is not supported yet.
 ## Requirements
 
 - Go 1.11+
@@ -97,4 +97,4 @@ for _, msg := range cr.Messages {
 ```
 
 ## Example
-Multiple Goroutines consumption is also supported. More specific examples can be referred in [Go Client Examples](https://github.com/apache/incubator-inlong/tree/master/inlong-tubemq/tubemq-client-twins/tubemq-client-go/example).
+Multiple Goroutines consumption is also supported. More specific examples can be referred in [Go Client Examples](https://github.com/apache/inlong/tree/master/inlong-tubemq/tubemq-client-twins/tubemq-client-go/example).

inlong-tubemq/tubemq-client-twins/tubemq-client-python/README.md

@@ -1,5 +1,5 @@
 ### TubeMQ Python Client
-TubeMQ Python Client library is a wrapper over the existing [C++ client library](https://github.com/apache/incubator-tubemq/tree/master/tubemq-client-twins/tubemq-client-cpp/) and exposes all of the same features.
+TubeMQ Python Client library is a wrapper over the existing [C++ client library](https://github.com/apache/inlong/tree/master/inlong-tubemq/tubemq-client-twins/tubemq-client-cpp/) and exposes all of the same features.
 
 #### Install from source
 ##### install python-devel

pom.xml

@@ -40,7 +40,7 @@
         to
         facilitate the construction of streaming-based data analysis, modeling, and applications.
     </description>
-    <url>https://github.com/apache/incubator-inlong</url>
+    <url>https://github.com/apache/inlong</url>
 
     <organization>
         <name>Apache Software Foundation</name>
@@ -50,7 +50,7 @@
 
     <developers>
         <developer>
-            <organization>Apache InLong(incubating) developers</organization>
+            <organization>Apache InLong developers</organization>
             <organizationUrl>https://inlong.apache.org/</organizationUrl>
         </developer>
     </developers>
@@ -64,20 +64,20 @@
     </licenses>
 
     <scm>
-        <url>https://github.com/apache/incubator-inlong</url>
-        <connection>scm:git:https://github.com/apache/incubator-inlong.git</connection>
-        <developerConnection>scm:git:ssh://[email protected]:apache/incubator-inlong.git
+        <url>https://github.com/apache/inlong</url>
+        <connection>scm:git:https://github.com/apache/inlong.git</connection>
+        <developerConnection>scm:git:ssh://[email protected]:apache/inlong.git
         </developerConnection>
     </scm>
 
     <ciManagement>
         <system>GitHub Actions</system>
-        <url>https://github.com/apache/incubator-inlong/actions</url>
+        <url>https://github.com/apache/inlong/actions</url>
     </ciManagement>
 
     <issueManagement>
         <system>Github</system>
-        <url>https://github.com/apache/incubator-inlong/issues</url>
+        <url>https://github.com/apache/inlong/issues</url>
     </issueManagement>
 
     <mailingLists>