Welcome to create pull requests or join in our mailing list for the bug fix, doc, example, suggestion and anything.
In Weex community all discussions happen on mailing list.
Just send an email to dev-subscribe@weex.incubator.apache.org
and follow the instructions to subscribe Weex dev mailing list. Then you will receive discussions and community messages with your personal email. You can also reply back or publish your opinions freely to join the community discussion.
You can also access the mail archives through the web portal.
To unsubscribe the mailing list: send an email to dev-unsubscribe@weex.incubator.apache.org
and follow the instructions.
Besides Weex dev mailing list channel, there are commits
and user
channels available for subscription. Check them out here.
rebase
instead of merge
when merging PRs when you work on a single branch, in order to keep it simple and clean for review.merge
when publishing beta and Apache release, or merging back changes on temporary branches back to master
branch.master
branchmaster
is the development branch, which tracks the bleeding-edge daily development works and is unstable from time to time.beta
branchBeta Release Channel
, each commit on this branch tracks a beta version, with a beta release tag
attached to it.release
branchrelease
is the Apache release publish branch, we take it as the project's Stable Release Channel
, each commit on it tracks a release version, with a release tag
attached to it.master
branch every Thursday evening to start a beta release, bug fixes for the release goes to this branch, and it will be released on the next Monday morning, after merging into the beta
branch, a beta release tag will be attached to the specific commit on beta
branch to identify a beta release.beta-0.xx.x
, a beta release can only grow the last digit of the version number as the beta version number.beta-0.xx.x
.beta
branch.beta
branch when we propose an Apache release, the frequency would be per month. We will follow the release process on this branch, including signoff, RC review, etc., after the Apache release vote, this branch will merge into release
branch and a release tag will be attached to the merge commit to identifying an Apache release version.rc-0.xx.0
, and it grows the middle digits as a release number.v0.xx.0
.release
branch.master
branch, and can only be merged back to master
branch when complete. It is not allowed to start a beta or Apache release from feature branch. It should be deleted soon after it is merged back to master
.[{module|issueID}] {title} {summary}
{module|issueID}
[Weex-xxx]
to track the changes for the issue.{title}
{summary}
A good commit log should look like this:
commit e110f0a32b6cfe6d0adb006a931f6d7fd9de7c01 Author: Adam Feng <cxfeng1@gmail.com> Date: Mon Jun 11 18:34:26 2018 +0800 [Script] release preparing: 1. add missing modules in package.json 2. move html5 folder to runtime folder in release_file.rules 3. modify js-framework path in build_from_source.sh 4. add NDK environment setup to HOW-TO-BUILD.md
You can create pull requests in GitHub.
*
operator goes with the variable name (e.g. Type *variable;)#pragma marks
to categorize methods into functional groupings and protocol implementations