Welcome to create pull requests or join in our mailing list for bugfix, doc, example, suggestion and anything.
In Weex community all discussion will 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. And then you will receive all discussions and community messages by your personal email. In the same time you can freely send your own emails to join in us.
At the same time you can see the archives of all the mails through the web: http://mail-archives.apache.org/mod_mbox/incubator-weex-dev/
If you won't follow the mailing list any more. There is another way to unsubscribe it: send an email to dev-unsubscribe@weex.incubator.apache.org
and follow the instructions.
Besides Weex dev mailing list, we also have some other mailing lists for you. You can check them out here: http://mail-archives.apache.org/mod_mbox/#weex.incubator
release ↑ {version} ↑ master <--- PR(feature/hotfix/typo)
master
branch 0. master
is the stable developing branch. 0. It's RECOMMENDED to commit hotfix (like typo) or feature PR to master
.{version}
branch 0. {version}
is used for every version which we consider for stable publish. 0. e.g. v0.16
release
branch 0. release
is the latest release branch,we will make tag and publish version on this branch.{module}-{action}-{shortName}
{module}
, see commit log module{action}
feature
: checkout from {module}
and merge to {module}
later. If {module}
not exists, merge to dev
bugfix
: like feature
, for bugfix onlyhotfix
: checkout from master
or release tag
, merge to master
and {module}
later. If {module}
not exists, merge to dev
for example:
android-bugfix-memory
jsfm-feature-communication
android-hotfix-compute-layout
{action} [{module}] {description}
{action}
+
add*
update or bugfix-
remove{module}
{description}
for example:
+ [android] close #123, add refreshing for WebView
* [doc] fix #123, update video auto-play property
- [example] remove abc
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