From b516640907843b8316da7b612984348ad346fcb1 Mon Sep 17 00:00:00 2001 From: yukon Date: Mon, 9 Oct 2017 18:16:39 +0800 Subject: [PATCH] [ROCKETMQ-302] TLP clean up, remove incubating related info and polish the release manual --- DISCLAIMER | 1 - NOTICE | 2 +- README.md | 4 +- _about/01-team.md | 2 +- _about/02-contact.md | 8 +- _config.yml | 8 +- _docs/01-quick-start-guide.md | 4 +- _docs/04-cli-admin-tool.md | 2 +- _docs/06-best-practice-pull-request.md | 42 +++---- _docs/08-release-manual.md | 117 ++++-------------- _docs/09-branching-model.md | 4 +- _docs/10-download-releases.md | 8 +- _docs/11-rocketmq-road-map.md | 12 +- _docs/24-how-to-contribute.md | 4 +- _docs/best-practice-create-pr.md | 28 ++--- _pages/community.md | 2 +- _pages/users.md | 2 +- ...stering-component-compatible-dependency.md | 2 +- ...017-01-05-launch-rocketmq-code-marathon.md | 6 +- ...17-01-24-release-notes-4.0.0-incubating.md | 4 +- ...rect-posture-of-submitting-pull-request.md | 16 +-- ...017-03-31-launch-rocketmq-code-marathon.md | 18 +-- apache-rocketmq-jekyll.gemspec | 2 +- home.md | 2 +- 24 files changed, 112 insertions(+), 188 deletions(-) delete mode 100644 DISCLAIMER diff --git a/DISCLAIMER b/DISCLAIMER deleted file mode 100644 index cf4d044461..0000000000 --- a/DISCLAIMER +++ /dev/null @@ -1 +0,0 @@ -Apache RocketMQ is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. diff --git a/NOTICE b/NOTICE index 5384857326..c218b26089 100644 --- a/NOTICE +++ b/NOTICE @@ -1,4 +1,4 @@ -Apache RocketMQ (incubating) +Apache RocketMQ Copyright 2016-2017 The Apache Software Foundation This product includes software developed at diff --git a/README.md b/README.md index 0e002cb527..298fe101fb 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ -# Apache RocketMQ (incubating) website +# Apache RocketMQ website -This is the website for [Apache RocketMQ]( http://rocketmq.apache.org/) (incubating). +This is the website for [Apache RocketMQ]( http://rocketmq.apache.org/). ## About This website is based on Jekyll and a Jekyll theme named Minimal Mistakes. diff --git a/_about/01-team.md b/_about/01-team.md index a1b7b5f320..5e730940c4 100644 --- a/_about/01-team.md +++ b/_about/01-team.md @@ -5,7 +5,7 @@ excerpt: "Project team." modified: 2016-12-28T19:55:43-04:00 --- -The RocketMQ team is comprised of Members and Contributors. Members have direct access to the source of RocketMQ project and actively evolve the code-base. Contributors improve the project through submission of patches and suggestions to the Members. The number of Contributors to the project is unbounded. All contributions to RocketMQ are greatly appreciated, whether for trivial cleanups, big new features or other material rewards. More details see [here](https://github.com/apache/incubator-rocketmq/blob/master/CONTRIBUTING.md). +The RocketMQ team is comprised of Members and Contributors. Members have direct access to the source of RocketMQ project and actively evolve the code-base. Contributors improve the project through submission of patches and suggestions to the Members. The number of Contributors to the project is unbounded. All contributions to RocketMQ are greatly appreciated, whether for trivial cleanups, big new features or other material rewards. More details see [here](https://github.com/apache/rocketmq/blob/master/CONTRIBUTING.md). ### Members diff --git a/_about/02-contact.md b/_about/02-contact.md index c1a2415cec..eae88f0379 100644 --- a/_about/02-contact.md +++ b/_about/02-contact.md @@ -12,10 +12,10 @@ These are the mailing lists that have been established for RocketMQ. For each li |Name|Description|Subscribe|Unsubscribe|Archive| |:---|:---|:---|:---|:---| -|Users|User support and questions mailing list| [Subscribe](mailto:users-subscribe@rocketmq.incubator.apache.org)|[Unsubscribe](mailto:users-unsubscribe@rocketmq.incubator.apache.org)|[mail-archives.apache.org](http://mail-archives.apache.org/mod_mbox/incubator-rocketmq-users/)| -|Issues|Mirror of all JIRA activity| [Subscribe](mailto:issues-subscribe@rocketmq.incubator.apache.org)|[Unsubscribe](mailto:issues-unsubscribe@rocketmq.incubator.apache.org)|[mail-archives.apache.org](http://mail-archives.apache.org/mod_mbox/incubator-rocketmq-issues/)| -|Development|Development related discussions|[Subscribe](mailto:dev-subscribe@rocketmq.incubator.apache.org)|[Unsubscribe](mailto:dev-unsubscribe@rocketmq.incubator.apache.org)|[mail-archives.apache.org](http://mail-archives.apache.org/mod_mbox/incubator-rocketmq-dev//)| -|Commits|All commits to repositories|[Subscribe](mailto:commits-subscribe@rocketmq.incubator.apache.org)|[Unsubscribe](mailto:commits-unsubscribe@rocketmq.incubator.apache.org)|[mail-archives.apache.org](http://mail-archives.apache.org/mod_mbox/incubator-rocketmq-commits/)| +|Users|User support and questions mailing list| [Subscribe](mailto:users-subscribe@rocketmq.apache.org)|[Unsubscribe](mailto:users-unsubscribe@rocketmq.apache.org)|[Mail Archives](https://lists.apache.org/list.html?users@rocketmq.apache.org)| +|Issues|Mirror of all JIRA activity| [Subscribe](mailto:issues-subscribe@rocketmq.apache.org)|[Unsubscribe](mailto:issues-unsubscribe@rocketmq.apache.org)|[Mail Archives](https://lists.apache.org/list.html?issues@rocketmq.apache.org)| +|Development|Development related discussions|[Subscribe](mailto:dev-subscribe@rocketmq.apache.org)|[Unsubscribe](mailto:dev-unsubscribe@rocketmq.apache.org)|[Mail Archives](https://lists.apache.org/list.html?dev@rocketmq.apache.org)| +|Commits|All commits to repositories|[Subscribe](mailto:commits-subscribe@rocketmq.apache.org)|[Unsubscribe](mailto:commits-unsubscribe@rocketmq.apache.org)|[Mail Archives](https://lists.apache.org/list.html?commits@rocketmq.apache.org)| ## Security Issues Tracking diff --git a/_config.yml b/_config.yml index 0e2424ad80..db2c5db0fb 100644 --- a/_config.yml +++ b/_config.yml @@ -13,7 +13,7 @@ name : "Apache RocketMQ" description : "The homepage of RocketMQ." url : # the base hostname & protocol for your site e.g. "https://mmistakes.github.io" baseurl : # the subpath of your site, e.g. "/blog" -repository : "apache/incubator-rocketmq" +repository : "apache/rocketmq" comment-repository : "zhouxinyu/rocketmq-comments" teaser : # path of fallback teaser image, e.g. "/assets/images/500x300.png" destination : content @@ -84,15 +84,15 @@ author: avatar : "/assets/images/rmq-logo.png" bio : "An open source distributed messaging and streaming data platform." location : "Hangzhou, China" - email : "dev@rocketmq.incubator.apache.org" - uri : "http://incubator.staging.apache.org/projects/rocketmq.html" + email : "dev@rocketmq.apache.org" + uri : "http://rocketmq.apache.org" bitbucket : codepen : dribbble : flickr : facebook : foursquare : - github : "apache/incubator-rocketmq" + github : "apache/rocketmq" google_plus : keybase : instagram : diff --git a/_docs/01-quick-start-guide.md b/_docs/01-quick-start-guide.md index 1cf9f55f50..3cd96a46ae 100644 --- a/_docs/01-quick-start-guide.md +++ b/_docs/01-quick-start-guide.md @@ -21,8 +21,8 @@ and receive messages. # Clone & Build ```shell - > git clone -b develop https://github.com/apache/incubator-rocketmq.git - > cd incubator-rocketmq + > git clone -b develop https://github.com/apache/rocketmq.git + > cd rocketmq > mvn -Prelease-all -DskipTests clean install -U > cd distribution/target/apache-rocketmq ``` diff --git a/_docs/04-cli-admin-tool.md b/_docs/04-cli-admin-tool.md index 943c8be460..fc326779bc 100644 --- a/_docs/04-cli-admin-tool.md +++ b/_docs/04-cli-admin-tool.md @@ -17,7 +17,7 @@ Make sure you have walked through [Quick Start](/docs/quick-start/) and [Core Co The admin tool is shipped along with RocketMQ. Whether you download a pre-built binary version or build from source by yourself, you have the tool with the package. -If you want to look at the source code, please refer to [rocketmq-tools module](https://github.com/apache/incubator-rocketmq/tree/master/tools) +If you want to look at the source code, please refer to [rocketmq-tools module](https://github.com/apache/rocketmq/tree/master/tools) # How to use diff --git a/_docs/06-best-practice-pull-request.md b/_docs/06-best-practice-pull-request.md index 0448732251..a63d4361df 100644 --- a/_docs/06-best-practice-pull-request.md +++ b/_docs/06-best-practice-pull-request.md @@ -9,9 +9,9 @@ This page guides you through Git setup and contribution process. {% include toc %} # Git setup for Contributors -First of all, fork github’s `apache/incubator-rocketmq` to your own account on github and clone it as follows, +First of all, fork github’s `apache/rocketmq` to your own account on github and clone it as follows, - git clone https://github.com//incubator-rocketmq.git + git clone https://github.com//rocketmq.git Cloning this locally will set up `origin` to point to your remote fork on github as the default remote. Now you can create your pull requests. @@ -19,7 +19,7 @@ Now you can create your pull requests. You will need to update a local master sometimes (to merge to your development branches). For this, you have to add remote for RocketMQ mirror as follows, - git remote add upstream https://github.com/apache/incubator-rocketmq.git + git remote add upstream https://github.com/apache/rocketmq.git and update your local master via `git fetch` followed by `git rebase`, for instance: git fetch upstream master @@ -28,7 +28,7 @@ and update your local master via `git fetch` followed by `git rebase`, for insta # Git setup for Committers In addition to contributors' configurations, committers will have to attach the apache git repo: - git remote add apache https://git-wip-us.apache.org/repos/asf/incubator-rocketmq.git + git remote add apache https://git-wip-us.apache.org/repos/asf/rocketmq.git To check your remote setup, issue @@ -36,12 +36,12 @@ To check your remote setup, issue You should see something like this: - origin https://github.com//incubator-rocketmq.git (fetch) - origin https://github.com//incubator-rocketmq.git (push) - upstream https://github.com/apache/incubator-rocketmq.git (fetch) - upstream https://github.com/apache/incubator-rocketmq.git (push) - apache https://git-wip-us.apache.org/repos/asf/incubator-rocketmq.git (fetch) - apache https://git-wip-us.apache.org/repos/asf/incubator-rocketmq.git (push) + origin https://github.com//rocketmq.git (fetch) + origin https://github.com//rocketmq.git (push) + upstream https://github.com/apache/rocketmq.git (fetch) + upstream https://github.com/apache/rocketmq.git (push) + apache https://git-wip-us.apache.org/repos/asf/rocketmq.git (fetch) + apache https://git-wip-us.apache.org/repos/asf/rocketmq.git (push) Now if you want to experiment with a branch everything, by default, points to your github account because 'origin' is default. You can work as normal using only github until you are ready to merge with the apache remote. Some conventions will integrate with Apache JIRA ticket numbers. @@ -63,11 +63,11 @@ Push your branch to Github: git checkout ROCKETMQ-xxxx git push origin ROCKETMQ-xxxx -1. Go to your ROCKETMQ-xxxx branch on Github. Since you forked it from Github's apache/incubator-rocketmq. By default all PR will go to apache/master. +1. Go to your ROCKETMQ-xxxx branch on Github. Since you forked it from Github's apache/rocketmq. By default all PR will go to apache/master. -2. Click the green "Compare, review, and create pull request" button. You can edit the to and from for the PR if it isn't correct. The "base fork" should be apache/incubator-rocketmq unless you are collaborating with one of the committers on the list. The "base" will be master. Don't submit a PR to any other branches unless permitted by branch owner. The "head fork" will be your forked repo and the "compare" will be your ROCKETMQ-xxxx branch. +2. Click the green "Compare, review, and create pull request" button. You can edit the to and from for the PR if it isn't correct. The "base fork" should be apache/rocketmq unless you are collaborating with one of the committers on the list. The "base" will be master. Don't submit a PR to any other branches unless permitted by branch owner. The "head fork" will be your forked repo and the "compare" will be your ROCKETMQ-xxxx branch. 3. Click the "Create pull request" button and name the request "ROCKETMQ-xxxx" all caps. This will connect the comments of the PR to the mailing list and JIRA comments. -4. From now on the PR lives on github's apache/incubator-rocketmq. You can use the commenting UI there. +4. From now on the PR lives on github's apache/rocketmq. You can use the commenting UI there. 5. If you are looking for a review or wanting to share with someone else please write a note in the comments and don't worry about automated merging of your PR -- you will have to do that later. The PR is tied to your branch so you can respond to comments, make fixes, and commit them from your local repo. They will appear on the PR page and be mirrored to JIRA and the mailing list. 6. When you are satisfied and want to push it to Apache's remote repo, you can merge this PR. @@ -79,7 +79,7 @@ Before you create a pull request, make sure For information about creating pull requests, please check [GitHub PR docs](https://help.github.com/articles/creating-a-pull-request/). -Pull requests are made to `apache/incubator-rocketmq` repository on Github. +Pull requests are made to `apache/rocketmq` repository on Github. In the Github UI you should pick the master branch as target of the PR.
You pull request will be reviewed and commented by committers, and issues can be discussed. When all reviewers are positive on the pull request, it will be merged. @@ -91,13 +91,13 @@ Each pull request should follow this checklist to help us incorporate your contr - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/projects/ROCKETMQ/issues/) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue. - [ ] Format the pull request title like `[ROCKETMQ-XXX] Fix UnknownException when host config not exist`. Each commit in the pull request should have a meaningful subject line and body. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. -- [ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in [test module](https://github.com/apache/incubator-rocketmq/tree/master/test). +- [ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in [test module](https://github.com/apache/rocketmq/tree/master/test). - [ ] Run `mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle` to make sure basic checks pass. Run `mvn clean install -DskipITs` to make sure unit-test pass. Run `mvn clean test-compile failsafe:integration-test` to make sure integration-test pass. - [ ] If this contribution is large, please file an [Apache Individual Contributor License Agreement](http://www.apache.org/licenses/#clas). ``` -Remember use `- [x]` mark an item finished in the check list and there is a [demo pull request](https://github.com/apache/incubator-rocketmq/pull/152) can be your reference. +Remember use `- [x]` mark an item finished in the check list and there is a [demo pull request](https://github.com/apache/rocketmq/pull/152) can be your reference. # Merging a PR (yours or contributors) Start with reading [GitHub PR merging locally](https://help.github.com/articles/checking-out-pull-requests-locally/). Remember that pull requests are equivalent to a remote github branch with potentially a multitude of commits. In this case it is recommended to squash remote commit history to have one commit per issue, rather than merging in a multitude of contributor's commits. In order to do that, as well as to close the PR at the same time, it is recommended to use squash commits. @@ -105,7 +105,7 @@ Merging pull requests are equivalent to a "pull" of a contributor's branch: git checkout master # switch to local master branch git pull apache master # fast-forward to current remote HEAD - git pull --squash https://github.com/cuser/incubator-rocketmq.git ROCKETMQ-xxxx # merge to master + git pull --squash https://github.com/cuser/rocketmq.git ROCKETMQ-xxxx # merge to master `--squash` ensures all PR history is squashed into single commit, and allows committer to use his/her own message. Please refer to git help for merge or pull for more information about `--squash` option. In this example we assume that the contributor's Github handle is "cuser" and the PR branch name is "ROCKETMQ-xxxx". Next, resolve all conflicts, or ask a contributor to rebase on top of master, if PR went out of sync. @@ -118,9 +118,9 @@ If you are ready to merge your own (committer's) PR you only need to merge (not Please run regular patch checks, build with tests enabled, and change CHANGELOG whenever needed. If all requirements are met, you can commit the squashed request using: - git commit --author="contributor_name " -a -m "ROCKETMQ-XXXX description closes apache/incubator-rocketmq#ZZ" + git commit --author="contributor_name " -a -m "ROCKETMQ-XXXX description closes apache/rocketmq#ZZ" -ROCKETMQ-XXXX is all capitalized and ZZ is the pull request number on apache/incubator-rocketmq repository. Including "closes apache/incubator-rocketmq#ZZ" will close the PR automatically. More information can be found here [GitHub PR closing docs.](https://help.github.com/articles/closing-issues-via-commit-messages/). +ROCKETMQ-XXXX is all capitalized and ZZ is the pull request number on apache/rocketmq repository. Including "closes apache/rocketmq#ZZ" will close the PR automatically. More information can be found here [GitHub PR closing docs.](https://help.github.com/articles/closing-issues-via-commit-messages/). Next, push to git-wip-us.apache.org: git push apache master @@ -135,10 +135,10 @@ Note on squashing: Since squash discards remote branch history, repeated PRs fro # Closing a PR without committing (for committers) When we want to reject a PR (close without committing), we can just issue an empty commit on master's HEAD without merging the PR: - git commit --allow-empty -m "ROCKETMQ-XXXX closes apache/incubator-rocketmq#ZZ *Won't fix*" + git commit --allow-empty -m "ROCKETMQ-XXXX closes apache/rocketmq#ZZ *Won't fix*" git push apache master -that should close PR ZZ on github mirror without merging and any code modifications in the master repository.more detail please refer to RocketMQ PR https://github.com/apache/incubator-rocketmq/pull/15 +that should close PR ZZ on github mirror without merging and any code modifications in the master repository.more detail please refer to RocketMQ PR https://github.com/apache/rocketmq/pull/15 # Apache/github integration features diff --git a/_docs/08-release-manual.md b/_docs/08-release-manual.md index 629753d703..e33e273d1b 100644 --- a/_docs/08-release-manual.md +++ b/_docs/08-release-manual.md @@ -7,7 +7,7 @@ modified: 2017-02-7T15:01:43-04:00 {% include toc %} -This is a guide to make a released version of Apache RocketMQ (incubating). Please follow the steps below: +This is a guide to make a released version of Apache RocketMQ. Please follow the steps below: ## Preliminaries ### Apache Release Documentation @@ -15,8 +15,6 @@ The release documentations provided by The ASF can be found here: * [Apache Release Guide](http://www.apache.org/dev/release-publishing) * [Apache Release Policy](http://www.apache.org/dev/release.html) -* [Apache Incubator Release Guidelines](http://incubator.apache.org/guides/releasemanagement.html) -* [Apache Incubator Release Policy](http://incubator.apache.org/incubation/Incubation_Policy.html#Releases) * [Maven Release Info](http://www.apache.org/dev/publishing-maven-artifacts.html) ### Code Signing Key @@ -26,7 +24,7 @@ Create a code signing gpg key for release signing, use **\@apac * Generate a new key via `gpg --gen-key`, and answer 4096 bits with no expiration time. * Upload your key to a public key server by `gpg --keyserver pgpkeys.mit.edu --send-key `. * Get the key signed by other committers(Optional). -* Add the key to the RocketMQ [KEYS file](https://dist.apache.org/repos/dist/dev/incubator/rocketmq/KEYS). +* Add the key to the RocketMQ [KEYS file](https://dist.apache.org/repos/dist/dev/rocketmq/KEYS). **Tips:** If you have more than one key in your gpg, set the code signing key to `~/.gnupg/gpg.conf` as default key is recommended. @@ -42,7 +40,7 @@ Make sure your Maven settings.xml file contains the following: forked-path yourKeyName yourApacheID - https://dist.apache.org/repos/dist/dev/incubator/rocketmq/ + https://dist.apache.org/repos/dist/dev/rocketmq/ @@ -73,10 +71,10 @@ Make sure your Maven settings.xml file contains the following: Cleanup JIRA issues related to this release version, and check all the issues has been marked with right version in the `FixVersion` field. ### Publish the Release Notes -Generate the release notes via [RocketMQ JIRA](https://issues.apache.org/jira/browse/ROCKETMQ/) and publish it to the [rocketmq-site](https://github.com/apache/incubator-rocketmq-site), there is a [release notes](http://rocketmq.apache.org/release_notes/release-notes-4.0.0-incubating/) of `4.0.0-incubating` available for reference, include the link to the release notes in the voting emails. +Generate the release notes via [RocketMQ JIRA](https://issues.apache.org/jira/browse/ROCKETMQ/) and publish it to the [rocketmq-site](https://github.com/apache/rocketmq-site), there is a [release notes](http://rocketmq.apache.org/release_notes/release-notes-4.0.0-incubating/) of `4.0.0-incubating` available for reference, include the link to the release notes in the voting emails. ## Build the Release Candidate -Firstly, checkout a new branch from `master` with its name equal to the release version, like `release-4.0.0-incubating`. +Firstly, checkout a new branch from `master` with its name equal to the release version, like `release-4.2.0`. ### Build the Candidate Release Artifacts Before building the release artifacts, do some verifications below: @@ -100,7 +98,6 @@ Now the release candidate is ready, before calling a vote, the artifacts must sa * Checksums and PGP signatures are valid. * Build is successful including unit and integration tests. -* DISCLAIMER is correct and filenames must include “incubating”. * LICENSE and NOTICE files are correct and dependency licenses are acceptable. * All source files have license headers and pass RAT checks. * Javadocs have been generated correctly. @@ -121,7 +118,7 @@ Please follow the steps below to verify the checksums and PGP signatures: or ```shell - gpg --verify rocketmq-all-%version-number%-incubating-source-release.zip.asc rocketmq-all-%version-number%-incubating-source-release.zip + gpg --verify rocketmq-all-%version-number%-source-release.zip.asc rocketmq-all-%version-number%-source-release.zip ``` Check the output to ensure it only contains good signatures: @@ -132,7 +129,7 @@ Please follow the steps below to verify the checksums and PGP signatures: 3. Compare MD5, SHA hash generated by the below command with the downloaded hash files. ```shell - gpg --print-mds rocketmq-all-%version-number%-incubating-source-release.zip + gpg --print-mds rocketmq-all-%version-number%-source-release.zip ``` ### Release Artifacts to Dev-Repository @@ -144,23 +141,23 @@ If the checks are passed, Nexus will close the repository and produce a URL to t If the checks aren't passed, fix the issues then go back and restart the release process. -If everything is ok, use svn to copy the candidate release artifacts to RocketMQ repo: https://dist.apache.org/repos/dist/dev/incubator/rocketmq/${release version}. +If everything is ok, use svn to copy the candidate release artifacts to RocketMQ repo: https://dist.apache.org/repos/dist/dev/rocketmq/${release version}. ## Vote on the Release -As per the Apache Incubator [release guidelines](http://incubator.apache.org/incubation/Incubation_Policy.html#Releases), all releases for incubating projects must go through a two-step voting process. First, release voting must successfully pass within the Apache RocketMQ community via the **dev@rocketmq.incubator.apache.org** mailing list. Then, release voting must successfully pass within the Apache Incubator PMC via the **general@incubator.apache.org** mailing list. +Release voting must successfully pass within the Apache RocketMQ community via the **dev@rocketmq.apache.org** mailing list. General information regarding the Apache voting process can be found [here](http://www.apache.org/foundation/voting.html). ### Apache RocketMQ Community Vote -To vote on a candidate release, send an email to the [dev list](mailto:dev@rocketmq.apache.incubator.org) with subject **[VOTE]: Release Apache RocketMQ \(incubating) RC\** and body: +To vote on a candidate release, send an email to the [dev list](mailto:dev@rocketmq.apache.org) with subject **[VOTE]: Release Apache RocketMQ \ RC\** and body: > Hello RocketMQ Community, > -> This is the vote for \ of Apache RocketMQ (incubating). +> This is the vote for \ of Apache RocketMQ. > > **The artifacts:** -> https://dist.apache.org/repos/dist/dev/incubator/rocketmq/${release version} +> https://dist.apache.org/repos/dist/dev/rocketmq/${release version} > > **The staging repo:** > https://repository.apache.org/content/repositories/orgapacherocketmq-XXX/ @@ -175,7 +172,7 @@ To vote on a candidate release, send an email to the [dev list](mailto:dev@rocke > \ > > The artifacts have been signed with Key : \, which can be found in the keys file: -> https://dist.apache.org/repos/dist/dev/incubator/rocketmq/KEYS +> https://dist.apache.org/repos/dist/dev/rocketmq/KEYS > > The vote will be open for at least 72 hours or until necessary number of votes are reached. > @@ -188,7 +185,7 @@ To vote on a candidate release, send an email to the [dev list](mailto:dev@rocke > Thanks, > The Apache RocketMQ Team -Once 72 hours has passed (which is generally preferred) and/or at least three +1 (binding) votes have been cast with no -1 (binding) votes, send an email closing the vote and congratulate the release candidate. Please use the subject: **[RESULT][VOTE]: Release Apache RocketMQ \(incubating) RC\** : +Once 72 hours has passed (which is generally preferred) and/or at least three +1 (binding) votes have been cast with no -1 (binding) votes, send an email closing the vote and congratulate the release candidate. Please use the subject: **[RESULT][VOTE]: Release Apache RocketMQ \ RC\** : > Hello RocketMQ Community, > @@ -204,107 +201,35 @@ Once 72 hours has passed (which is generally preferred) and/or at least three +1 > User Name (Apache ID) > .... > -> A vote Apache RocketMQ \ will now be called on general@incubator.apache.org. +> The release will be published soon. > > Thanks, > The Apache RocketMQ Team -If we do not pass the VOTE, fix the related issues, go back, restart the release process and increase RC number. When we call a new vote, we must use the updated mail subject: **[RESTART][VOTE][#\]: Release Apache RocketMQ \(incubating) RC\** - -### Incubator PMC Vote -Once the candidate release vote passes on dev@rocketmq, send an email to [IMPC](mailto:general@incubator.apache.org) with subject **[VOTE]: Release Apache RocketMQ \(incubating) RC\** and a body along the lines of: - -> Hello Incubator PMC, -> -> The Apache RocketMQ community has voted and approved the proposal to release Apache RocketMQ \ (incubating). We now kindly request the IPMC review and vote on this incubator release. -> -> **[VOTE] Thread:** -> \ -> -> **[RESULT][VOTE] Thread:** -> \ -> -> **The artifacts:** -> https://dist.apache.org/repos/dist/dev/incubator/rocketmq/${release version} -> -> **The staging repo:** -> https://repository.apache.org/content/repositories/orgapacherocketmq-XXX/ -> -> **Git tag for the release:** -> \ -> -> **Hash for the release tag:** -> \ -> -> **Release Notes:** -> \ -> -> The artifacts have been signed with Key : \, which can be found in the keys file: -> https://dist.apache.org/repos/dist/dev/incubator/rocketmq/KEYS -> -> The vote will be open for at least 72 hours or until necessary number of votes are reached. -> -> Please vote accordingly: -> -> [ ] +1 approve -> [ ] +0 no opinion -> [ ] -1 disapprove with the reason -> -> Thanks, -> The Apache RocketMQ Team - -Also don't forget to announce the vote result: - -> Hello Incubator PMC, -> -> The Apache RocketMQ vote is now closed and has passed wit [number] binding +1s, [number] non-binding +1s and no 0 or -1: -> -> **Binding votes +1s:** -> User Name (Apache ID) -> User Name (Apache ID) -> User Name (Apache ID) -> .... -> -> **Non-binding votes +1s:** -> User Name (Apache ID) -> .... -> -> The Apache RocketMQ (incubating) community will proceed with the release. -> -> Thanks, -> The Apache RocketMQ Team +If we do not pass the VOTE, fix the related issues, go back, restart the release process and increase RC number. When we call a new vote, we must use the updated mail subject: **[RESTART][VOTE][#\]: Release Apache RocketMQ \ RC\** ## Publish the Release -Once the Apache RocketMQ PPMC and IPMC votes both pass, publish the release artifacts to the Nexus Maven repository and to the Apache release repository. +Once the Apache RocketMQ PPMC votes pass, publish the release artifacts to the Nexus Maven repository and to the Apache release repository. 1. Publish the Maven Artifacts, release the Maven artifacts in Nexus by selecting the staging repository **orgapacherocketmq-XXX** and clicking on the `Release` icon. -2. Publish the Artifacts to the Apache Release Repository, use svn copy candidate release artifacts to https://dist.apache.org/repos/dist/release/incubator/rocketmq/${release version} +2. Publish the Artifacts to the Apache Release Repository, use svn copy candidate release artifacts to https://dist.apache.org/repos/dist/release/rocketmq/${release version} ## Announce the Release -Send an email to **announce@apache.org**, **general@incubator.apache.org**, and **dev@rocketmq.apache.incubator.org** with the subject **[ANNOUNCE] Release Apache RocketMQ \(incubating)** and a body along the lines of: +Send an email to **announce@apache.org**, and **dev@rocketmq.apache.org** with the subject **[ANNOUNCE] Release Apache RocketMQ \** and a body along the lines of: > Hi all, > -> The Apache RocketMQ team would like to announce the release of Apache RocketMQ \ (incubating). +> The Apache RocketMQ team would like to announce the release of Apache RocketMQ \. > > More details regarding Apache RocketMQ can be found at: > http://rocketmq.apache.org/ > > The release artifacts can be downloaded here: -> https://dist.apache.org/repos/dist/release/incubator/rocketmq/${release version} +> https://dist.apache.org/repos/dist/release/rocketmq/${release version} > > The release notes can be found here: > \ > > Thanks, > The Apache RocketMQ Team -> -> --- DISCLAIMER Apache RocketMQ is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code,it does indicate that the project has yet to be fully endorsed by the ASF. - -## References - -[1]. http://pirk.incubator.apache.org/releasing -[2]. http://htrace.incubator.apache.org/building.html -[3]. http://slider.incubator.apache.org/developing/releasing.html -[4]. http://streams.incubator.apache.org/release-management.html diff --git a/_docs/09-branching-model.md b/_docs/09-branching-model.md index 9bde9c4db3..9c98cd77b0 100644 --- a/_docs/09-branching-model.md +++ b/_docs/09-branching-model.md @@ -118,8 +118,8 @@ It is exactly at the start of a release branch that the upcoming release gets as Release branches are created from the develop branch: ```shell -$ git checkout -b release-4.0.0-incubating develop -Switched to a new branch "release-4.0.0-incubating" +$ git checkout -b release-4.2.0 develop +Switched to a new branch "release-4.2.0" ``` Please refer to [here](/docs/release-manual) for the following process. diff --git a/_docs/10-download-releases.md b/_docs/10-download-releases.md index cca3028093..eb2cdf4ff8 100644 --- a/_docs/10-download-releases.md +++ b/_docs/10-download-releases.md @@ -17,11 +17,11 @@ Use the links below to download the Apache RocketMQ Releases, the latest release ## 4.1.0-incubating release -* Source: [rocketmq-all-4.1.0-incubating-source-release.zip](https://www.apache.org/dyn/closer.cgi?path=incubator/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-source-release.zip) [[PGP](https://www.apache.org/dist/incubator/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-source-release.zip.asc)] [[MD5](https://www.apache.org/dist/incubator/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-source-release.zip.md5)] [[SHA1](https://www.apache.org/dist/incubator/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-source-release.zip.sha1)] -* Binary: [rocketmq-all-4.1.0-incubating-bin-release.zip](https://www.apache.org/dyn/closer.cgi?path=incubator/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-bin-release.zip) [[PGP](https://www.apache.org/dist/incubator/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-bin-release.zip.asc)] [[MD5](https://www.apache.org/dist/incubator/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-bin-release.zip.md5)] [[SHA1](https://www.apache.org/dist/incubator/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-bin-release.zip.sha1)] +* Source: [rocketmq-all-4.1.0-incubating-source-release.zip](https://www.apache.org/dyn/closer.cgi?path=rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-source-release.zip) [[PGP](https://www.apache.org/dist/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-source-release.zip.asc)] [[MD5](https://www.apache.org/dist/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-source-release.zip.md5)] [[SHA1](https://www.apache.org/dist/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-source-release.zip.sha1)] +* Binary: [rocketmq-all-4.1.0-incubating-bin-release.zip](https://www.apache.org/dyn/closer.cgi?path=rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-bin-release.zip) [[PGP](https://www.apache.org/dist/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-bin-release.zip.asc)] [[MD5](https://www.apache.org/dist/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-bin-release.zip.md5)] [[SHA1](https://www.apache.org/dist/rocketmq/4.1.0-incubating/rocketmq-all-4.1.0-incubating-bin-release.zip.sha1)] ## 4.0.0-incubating release -* Source: [rocketmq-all-4.0.0-incubating-source-release.zip](https://www.apache.org/dyn/closer.cgi?path=incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip) [[PGP](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.asc)] [[MD5](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.md5)] [[SHA1](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.sha1)] -* Binary: [rocketmq-all-4.0.0-incubating-bin-release.zip](https://www.apache.org/dyn/closer.cgi?path=incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip) [[PGP](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.asc)] [[MD5](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.md5)] [[SHA1](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.sha1)] +* Source: [rocketmq-all-4.0.0-incubating-source-release.zip](https://www.apache.org/dyn/closer.cgi?path=rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip) [[PGP](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.asc)] [[MD5](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.md5)] [[SHA1](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.sha1)] +* Binary: [rocketmq-all-4.0.0-incubating-bin-release.zip](https://www.apache.org/dyn/closer.cgi?path=rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip) [[PGP](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.asc)] [[MD5](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.md5)] [[SHA1](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.sha1)] diff --git a/_docs/11-rocketmq-road-map.md b/_docs/11-rocketmq-road-map.md index 76a25815d5..d00dbb5845 100644 --- a/_docs/11-rocketmq-road-map.md +++ b/_docs/11-rocketmq-road-map.md @@ -23,7 +23,7 @@ So, we want to define and implement a reasonable filter language based on a subs ### Batch Messaging -In order to use RocketMQ in big data related scenarios, batch messaging is necessary and will bring million-level TPS for RocketMQ. [JIRA](https://issues.apache.org/jira/browse/ROCKETMQ-80), [PR](https://github.com/apache/incubator-rocketmq/pull/53) +In order to use RocketMQ in big data related scenarios, batch messaging is necessary and will bring million-level TPS for RocketMQ. [JIRA](https://issues.apache.org/jira/browse/ROCKETMQ-80), [PR](https://github.com/apache/rocketmq/pull/53) ### Consistent Hash Allocate Strategy(CHAS) @@ -31,7 +31,7 @@ Consumer clients use the average allocate strategy by far, which is very sensiti A Consistent Hash allocate strategy is valuable for developers who care more about stabilization than averaging. -So we decided to support CHAS as an extra choice in consumer load balancing. [JIRA](https://issues.apache.org/jira/browse/ROCKETMQ-67), [PR](https://github.com/apache/incubator-rocketmq/pull/67) +So we decided to support CHAS as an extra choice in consumer load balancing. [JIRA](https://issues.apache.org/jira/browse/ROCKETMQ-67), [PR](https://github.com/apache/rocketmq/pull/67) ### Global Order Messaging @@ -64,7 +64,7 @@ Provide a docker image for easy deployment and management, optimize for the late ### MQTT MQTT is a machine-to-machine (M2M)/"Internet of Things" connectivity protocol, which has been widely used in IoT. Support MQTT, give RocketMQ the power to connect everything. [JIRA](https://issues.apache.org/jira/browse/ROCKETMQ-127) -## 4.4.0-incubating+ RoadMap: +## 4.4.0+ RoadMap: 1. Support more application layer protocol: WebSocket, HTTP2, etc. 2. Support more native language SDK: PHP, Python, .Net, Node, Go, etc. The chosen programming languages are based on the investigation of many cloud platforms. @@ -74,9 +74,9 @@ MQTT is a machine-to-machine (M2M)/"Internet of Things" connectivity protocol, w RocketMQ, as a message-oriented middleware, plays a connector role in distributed environment, so in order to embrace the ecological preferably, RocketMQ community needs a series of external projects to integrate with other excellent projects. -1. rocketmq-console, provide a ops dashboard for RocketMQ. [REPO](https://github.com/apache/incubator-rocketmq-externals/tree/master/rocketmq-console) -2. rocketmq-jms, provide a new client to support JMS 2.0. [REPO](https://github.com/apache/incubator-rocketmq-externals/tree/master/rocketmq-jms) -3. rocketmq-flume-ng, integrate RocketMQ with Apache Flume.[REPO](https://github.com/apache/incubator-rocketmq-externals/tree/master/rocketmq-flume), [FLUME-JIRA](https://issues.apache.org/jira/browse/FLUME-3058) +1. rocketmq-console, provide a ops dashboard for RocketMQ. [REPO](https://github.com/apache/rocketmq-externals/tree/master/rocketmq-console) +2. rocketmq-jms, provide a new client to support JMS 2.0. [REPO](https://github.com/apache/rocketmq-externals/tree/master/rocketmq-jms) +3. rocketmq-flume-ng, integrate RocketMQ with Apache Flume.[REPO](https://github.com/apache/rocketmq-externals/tree/master/rocketmq-flume), [FLUME-JIRA](https://issues.apache.org/jira/browse/FLUME-3058) 4. rocketmq-storm, integrate RocketMQ with storm. [REPO](https://github.com/rocketmq/rocketmq-storm) 5. rocketmq-ignite, integrate RocketMQ with ignite. [JIRA](https://issues.apache.org/jira/browse/ROCKETMQ-41), [IGNITE-JIRA](https://issues.apache.org/jira/browse/IGNITE-4539) 6. rocketmq-spark, integrate RocketMQ with spark. [JIRA](https://issues.apache.org/jira/browse/ROCKETMQ-81) diff --git a/_docs/24-how-to-contribute.md b/_docs/24-how-to-contribute.md index c49f2110bf..3c1da24fb6 100644 --- a/_docs/24-how-to-contribute.md +++ b/_docs/24-how-to-contribute.md @@ -60,7 +60,7 @@ We maintain a list of all known bugs, proposed improvements and suggested featur Good documentation is crucial for any kind of software. The Apache RocketMQ community aims to provide concise, precise, and complete documentation and welcomes any contribution to improve Apache RocketMQ’s documentation. * Please report missing, incorrect, or out-dated documentation as a [JIRA ISSUE](https://issues.apache.org/jira/projects/ROCKETMQ). -* RocketMQ’s documentation is written in Markdown and located in the docs folder in RocketMQ’s [site source code repository](https://github.com/apache/incubator-rocketmq-site). See the Contribute [documentation guidelines](/docs/code-guidelines/) for detailed instructions for how to update and improve the documentation and to contribute your changes. +* RocketMQ’s documentation is written in Markdown and located in the docs folder in RocketMQ’s [site source code repository](https://github.com/apache/rocketmq-site). See the Contribute [documentation guidelines](/docs/code-guidelines/) for detailed instructions for how to update and improve the documentation and to contribute your changes. ## Improve the website @@ -73,7 +73,7 @@ The Apache RocketMQ website presents Apache RocketMQ and its community. It serve We welcome any contribution to improve our website. Please open a [JIRA issue](https://issues.apache.org/jira/projects/ROCKETMQ) if you think our website could be improved. -Please follow the Improve the [website guidelines](https://github.com/apache/incubator-rocketmq-site) if you would like to update and improve the website. +Please follow the Improve the [website guidelines](https://github.com/apache/rocketmq-site) if you would like to update and improve the website. ## More ways to contribute… diff --git a/_docs/best-practice-create-pr.md b/_docs/best-practice-create-pr.md index aeced4ff96..2eff18e523 100644 --- a/_docs/best-practice-create-pr.md +++ b/_docs/best-practice-create-pr.md @@ -9,9 +9,9 @@ This page guides you through the pull request creation process. {% include toc %} # Git setup for Contributors -First of all, fork github’s `apache/incubator-rocketmq` to your own account on github and clone it as follows, +First of all, fork github’s `apache/rocketmq` to your own account on github and clone it as follows, - git clone https://github.com//incubator-rocketmq.git + git clone https://github.com//rocketmq.git Cloning this locally will set up `origin` to point to your remote fork on github as the default remote. Now you can create your pull requests. @@ -19,7 +19,7 @@ Now you can create your pull requests. You will need to update a local master sometimes (to merge to your development branches sometimes). For this, you have to add remote for RocketMQ mirror as follows, - git remote add upstream https://github.com/apache/incubator-rocketmq.git + git remote add upstream https://github.com/apache/rocketmq.git and update your local master via `git fetch` followed by `git rebase`, for instance: git fetch upstream master @@ -28,7 +28,7 @@ and update your local master via `git fetch` followed by `git rebase`, for insta # Git setup for Committers In addition to contributors' configurations, committers will have to attach the apache git repo: - git remote add apache https://git-wip-us.apache.org/repos/asf/incubator-rocketmq.git + git remote add apache https://git-wip-us.apache.org/repos/asf/rocketmq.git To check your remote setup, issue @@ -36,12 +36,12 @@ To check your remote setup, issue You should see something like this: - origin https://github.com//incubator-rocketmq.git (fetch) - origin https://github.com//incubator-rocketmq.git (push) - upstream https://github.com/apache/incubator-rocketmq.git (fetch) - upstream https://github.com/apache/incubator-rocketmq.git (push) - apache https://git-wip-us.apache.org/repos/asf/incubator-rocketmq.git (fetch) - apache https://git-wip-us.apache.org/repos/asf/incubator-rocketmq.git (push) + origin https://github.com//rocketmq.git (fetch) + origin https://github.com//rocketmq.git (push) + upstream https://github.com/apache/rocketmq.git (fetch) + upstream https://github.com/apache/rocketmq.git (push) + apache https://git-wip-us.apache.org/repos/asf/rocketmq.git (fetch) + apache https://git-wip-us.apache.org/repos/asf/rocketmq.git (push) Now if you want to experiment with a branch everything, by default, points to your github account because 'origin' is default. You can work as normal using only github until you are ready to merge with the apache remote. Some conventions will integrate with Apache JIRA ticket numbers. @@ -63,11 +63,11 @@ Push your branch to Github: git checkout ROCKETMQ-xxxx git push origin ROCKETMQ-xxxx -1. Go to your ROCKETMQ-xxxx branch on Github. Since you forked it from Github's apache/incubator-rocketmq. By default all PR will go to apache/master. +1. Go to your ROCKETMQ-xxxx branch on Github. Since you forked it from Github's apache/rocketmq. By default all PR will go to apache/master. -2. Click the green "Compare, review, and create pull request" button. You can edit the to and from for the PR if it isn't correct. The "base fork" should be apache/incubator-rocketmq unless you are collaborating with one of the committers on the list. The "base" will be master. Don't submit a PR to any other branches unless permitted by branch owner. The "head fork" will be your forked repo and the "compare" will be your ROCKETMQ-xxxx branch. +2. Click the green "Compare, review, and create pull request" button. You can edit the to and from for the PR if it isn't correct. The "base fork" should be apache/rocketmq unless you are collaborating with one of the committers on the list. The "base" will be master. Don't submit a PR to any other branches unless permitted by branch owner. The "head fork" will be your forked repo and the "compare" will be your ROCKETMQ-xxxx branch. 3. Click the "Create pull request" button and name the request "ROCKETMQ-xxxx" all caps. This will connect the comments of the PR to the mailing list and JIRA comments. -4. From now on the PR lives on github's apache/incubator-rocketmq. You can use the commenting UI there. +4. From now on the PR lives on github's apache/rocketmq. You can use the commenting UI there. 5. If you are looking for a review or wanting to share with someone else please write a note in the comments and don't worry about automated merging of your PR -- you will have to do that later. The PR is tied to your branch so you can respond to comments, make fixes, and commit them from your local repo. They will appear on the PR page and be mirrored to JIRA and the mailing list. 6. When you are satisfied and want to push it to Apache's remote repo, you can merge this PR. @@ -79,6 +79,6 @@ Before you create a pull request, make sure For information about creating pull requests, please check [GitHub PR docs](https://help.github.com/articles/creating-a-pull-request/). -Pull requests are made to `apache/incubator-rocketmq` repository on Github. +Pull requests are made to `apache/rocketmq` repository on Github. In the Github UI you should pick the master branch as target of the PR.
You pull request will be reviewed and commented by committers, and issues can be discussed. When all reviewers are positive on the pull request, it will be merged. \ No newline at end of file diff --git a/_pages/community.md b/_pages/community.md index 70b5e5d175..26365fa89f 100644 --- a/_pages/community.md +++ b/_pages/community.md @@ -8,7 +8,7 @@ header: cta_label: " Getting Started" cta_url: "/docs/quick-start/" caption: -excerpt: 'Apache RocketMQ™ is an open source distributed messaging and streaming data platform.
Latest release v4.0.0-incubating

{::nomarkdown} {:/nomarkdown}' +excerpt: 'Apache RocketMQ™ is an open source distributed messaging and streaming data platform.
Latest release v4.1.0-incubating

{::nomarkdown} {:/nomarkdown}' --- {% include feature_row id="intro" type="center" %} diff --git a/_pages/users.md b/_pages/users.md index b4f8443db6..ab476e9c5d 100644 --- a/_pages/users.md +++ b/_pages/users.md @@ -8,7 +8,7 @@ header: cta_label: " Getting Started" cta_url: "/docs/quick-start/" caption: -excerpt: 'Apache RocketMQ™ is an open source distributed messaging and streaming data platform.
Latest release v4.0.0-incubating

{::nomarkdown} {:/nomarkdown}' +excerpt: 'Apache RocketMQ™ is an open source distributed messaging and streaming data platform.
Latest release v4.1.0-incubating

{::nomarkdown} {:/nomarkdown}' feature_row: - image_path: /assets/images/community/alibaba-logo.png alt: "Alibaba Group" diff --git a/_posts/2016-12-23-mastering-component-compatible-dependency.md b/_posts/2016-12-23-mastering-component-compatible-dependency.md index 02c0f5eb2c..8f62eff5a3 100644 --- a/_posts/2016-12-23-mastering-component-compatible-dependency.md +++ b/_posts/2016-12-23-mastering-component-compatible-dependency.md @@ -265,4 +265,4 @@ In **Dependency Mediator** 2.0 version,you could customize version differentiati Through this article, you almost calculated the evolution process of the **Dependency Mediator** project.in my opinion,integration with the maven enforcer plugin may be a better choice.After all,I hope **Dependency Mediator** can keep sustainable development.I would try and donate this project to codehaus in the near future. -If you have better idea or improving suggestion, please contact . +If you have better idea or improving suggestion, please contact . diff --git a/_posts/2017-01-05-launch-rocketmq-code-marathon.md b/_posts/2017-01-05-launch-rocketmq-code-marathon.md index 80f871df2d..551a211312 100644 --- a/_posts/2017-01-05-launch-rocketmq-code-marathon.md +++ b/_posts/2017-01-05-launch-rocketmq-code-marathon.md @@ -31,15 +31,15 @@ tags: 1. Brand New UI 1. I18n Support 1. [Spring Boot](https://projects.spring.io/spring-boot/) + [Bootstrap](http://getbootstrap.com/) Recommended -1. Join by Creating Pull Requests against [RocketMQ Console Repository](https://github.com/apache/incubator-rocketmq-externals/tree/master/rocketmq-console) +1. Join by Creating Pull Requests against [RocketMQ Console Repository](https://github.com/apache/rocketmq-externals/tree/master/rocketmq-console) ### RocketMQ-JMS 1. Supporting JMS 2.0 Protocol 1. Rich Documentation and Good Test Cases Coverage -1. Join by Creating Pull Requests against [RocketMQ JMS Repository](https://github.com/apache/incubator-rocketmq-externals/tree/master/rocketmq-jms) +1. Join by Creating Pull Requests against [RocketMQ JMS Repository](https://github.com/apache/rocketmq-externals/tree/master/rocketmq-jms) ### RocketMQ-Flume 1. Supporting Latest [Flume](http://flume.apache.org/) 1. Rich Documentation and Good Test Cases Coverage -1. Join by Creating Pull Requests against [RocketMQ Flume Repository](https://github.com/apache/incubator-rocketmq-externals/tree/master/rocketmq-flume) +1. Join by Creating Pull Requests against [RocketMQ Flume Repository](https://github.com/apache/rocketmq-externals/tree/master/rocketmq-flume) diff --git a/_posts/2017-01-24-release-notes-4.0.0-incubating.md b/_posts/2017-01-24-release-notes-4.0.0-incubating.md index 8f58f0c63a..76c6d8d45f 100644 --- a/_posts/2017-01-24-release-notes-4.0.0-incubating.md +++ b/_posts/2017-01-24-release-notes-4.0.0-incubating.md @@ -13,8 +13,8 @@ Below is a summary of the JIRA issues addressed in the 4.0.0-incubating release

Download the 4.0.0-incubating release

-* Source: [rocketmq-all-4.0.0-incubating-source-release.zip](https://www.apache.org/dyn/closer.cgi?path=incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip) [[PGP](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.asc)] [[MD5](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.md5)] [[SHA1](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.sha1)] -* Binary: [rocketmq-all-4.0.0-incubating-bin-release.zip](https://www.apache.org/dyn/closer.cgi?path=incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip) [[PGP](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.asc)] [[MD5](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.md5)] [[SHA1](https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.sha1)] +* Source: [rocketmq-all-4.0.0-incubating-source-release.zip](https://www.apache.org/dyn/closer.cgi?path=rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip) [[PGP](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.asc)] [[MD5](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.md5)] [[SHA1](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.sha1)] +* Binary: [rocketmq-all-4.0.0-incubating-bin-release.zip](https://www.apache.org/dyn/closer.cgi?path=rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip) [[PGP](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.asc)] [[MD5](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.md5)] [[SHA1](https://www.apache.org/dist/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.sha1)]

Bug diff --git a/_posts/2017-03-24-the-correct-posture-of-submitting-pull-request.md b/_posts/2017-03-24-the-correct-posture-of-submitting-pull-request.md index dafdcb2775..6bb9023fd3 100644 --- a/_posts/2017-03-24-the-correct-posture-of-submitting-pull-request.md +++ b/_posts/2017-03-24-the-correct-posture-of-submitting-pull-request.md @@ -6,19 +6,19 @@ ![](http://img3.tbcdn.cn/5476e8b07b923/TB17G5kQpXXXXcUapXXXXXXXXXX) Click the "fork" button, a forked repo will be added to your repo list. * clone the forked repo, here take "foo" as example -> git clone https://github.com/foo/incubator-rocketmq.git +> git clone https://github.com/foo/rocketmq.git * add apache remote repo -> git remote add apache https://github.com/apache/incubator-rocketmq.git +> git remote add apache https://github.com/apache/rocketmq.git * show the remote repos > git remote -v -> apache https://github.com/apache/incubator-rocketmq.git (fetch) -> apache https://github.com/apache/incubator-rocketmq.git (push) -> origin https://github.com/foo/incubator-rocketmq.git (fetch) -> origin https://github.com/foo/incubator-rocketmq.git (push) +> apache https://github.com/apache/rocketmq.git (fetch) +> apache https://github.com/apache/rocketmq.git (push) +> origin https://github.com/foo/rocketmq.git (fetch) +> origin https://github.com/foo/rocketmq.git (push) -**Note**: https://github.com/apache/incubator-rocketmq.git is a read-only repo, mirrored from git://git.apache.org/incubator-rocketmq.git. For submitting PR, fork this read-only repo on Github is OK. +**Note**: https://github.com/apache/rocketmq.git is a read-only repo, mirrored from git://git.apache.org/rocketmq.git. For submitting PR, fork this read-only repo on Github is OK. ### Use a new branch to write your own code and commit you'd better use a new branch for each PR, for it is convenient to manage your code and commits @@ -64,6 +64,6 @@ For example: For now, we have finished the preparations of a PR. It is time to create it. For apache projects, we could attach the jira issue using specific title like "[XXX] add something", such as "[ROCKETMQ-80] Add batch feature", the "XXX" represents the the name of the jira issue. you could refer to: -[https://github.com/apache/incubator-rocketmq/pull/53](https://github.com/apache/incubator-rocketmq/pull/53) +[https://github.com/apache/rocketmq/pull/53](https://github.com/apache/rocketmq/pull/53) diff --git a/_posts/2017-03-31-launch-rocketmq-code-marathon.md b/_posts/2017-03-31-launch-rocketmq-code-marathon.md index 88749357df..28b535809f 100644 --- a/_posts/2017-03-31-launch-rocketmq-code-marathon.md +++ b/_posts/2017-03-31-launch-rocketmq-code-marathon.md @@ -29,24 +29,24 @@ tags: 1. Integration of big data analysis framework 1. Rich Documentation and Good Test Cases Coverage 1. Apache Beam preferred -2. Join by Creating Pull Requests against [RocketMQ Beam Repository](https://github.com/apache/incubator-rocketmq-externals) -3. Join by Creating Pull Requests against [RocketMQ Flink Repository](https://github.com/apache/incubator-rocketmq-externals) +2. Join by Creating Pull Requests against [RocketMQ Beam Repository](https://github.com/apache/rocketmq-externals) +3. Join by Creating Pull Requests against [RocketMQ Flink Repository](https://github.com/apache/rocketmq-externals) 4. Join by Existing Pull Request against [RocketMQ Storm Repository](https://github.com/apache/storm/pull/2024) -4. Join by Existing Pull Request against [RocketMQ Spark Repository](https://github.com/apache/incubator-rocketmq-externals/pull/5) +4. Join by Existing Pull Request against [RocketMQ Spark Repository](https://github.com/apache/rocketmq-externals/pull/5) ### RocketMQ-Client SDK 1. Development of RocketMQ Client 1. Rich Documentation and Good Test Cases Coverage 3. Go preferred -1. Join by Creating Pull Requests against [RocketMQ Go Repository](https://github.com/apache/incubator-rocketmq-externals) -2. Join by Creating Pull Requests against [RocketMQ .Net Repository](https://github.com/apache/incubator-rocketmq-externals) -3. Join by Creating Pull Requests against [RocketMQ PHP Repository](https://github.com/apache/incubator-rocketmq-externals) +1. Join by Creating Pull Requests against [RocketMQ Go Repository](https://github.com/apache/rocketmq-externals) +2. Join by Creating Pull Requests against [RocketMQ .Net Repository](https://github.com/apache/rocketmq-externals) +3. Join by Creating Pull Requests against [RocketMQ PHP Repository](https://github.com/apache/rocketmq-externals) ### RocketMQ-Data Replication 1. Implement Data Replication from Database 1. Rich Documentation and Good Test Cases Coverage 3. MySQL preferred -1. Join by Creating Pull Requests against [RocketMQ MySQL Repository](https://github.com/apache/incubator-rocketmq-externals) -2. Join by Creating Pull Requests against [RocketMQ Redis Repository](https://github.com/apache/incubator-rocketmq-externals) -3. Join by Creating Pull Requests against [RocketMQ MongoDB Repository](https://github.com/apache/incubator-rocketmq-externals) +1. Join by Creating Pull Requests against [RocketMQ MySQL Repository](https://github.com/apache/rocketmq-externals) +2. Join by Creating Pull Requests against [RocketMQ Redis Repository](https://github.com/apache/rocketmq-externals) +3. Join by Creating Pull Requests against [RocketMQ MongoDB Repository](https://github.com/apache/rocketmq-externals) diff --git a/apache-rocketmq-jekyll.gemspec b/apache-rocketmq-jekyll.gemspec index f2d4a41a71..f5288ac19a 100644 --- a/apache-rocketmq-jekyll.gemspec +++ b/apache-rocketmq-jekyll.gemspec @@ -6,7 +6,7 @@ Gem::Specification.new do |spec| spec.authors = ["Michael Rose"] spec.summary = %q{A flexible two-column Jekyll theme.} - spec.homepage = "https://github.com/apache/incubator-rocketmq/" + spec.homepage = "https://github.com/apache/rocketmq/" spec.license = "MIT" spec.metadata["plugin_type"] = "theme" diff --git a/home.md b/home.md index 36f8081035..e1c21fd90b 100644 --- a/home.md +++ b/home.md @@ -7,7 +7,7 @@ header: cta_label: " Getting Started" cta_url: "/docs/quick-start/" caption: -excerpt: 'Apache RocketMQ™ is an open source distributed messaging and streaming data platform.
Latest release v4.1.0-incubating

{::nomarkdown} {:/nomarkdown}' +excerpt: 'Apache RocketMQ™ is an open source distributed messaging and streaming data platform.
Latest release v4.1.0-incubating

{::nomarkdown} {:/nomarkdown}' feature_row: - image_path: /assets/images/rmq-feature-lowlatency.png alt: "Low Latency"