If you have any comment or advice, please report your issue, or make any change as you wish and submit a PR.
- Please specify what kind of issue it is.
- Before you report an issue, please search for related issues. Make sure you are not going to open a duplicate issue.
- Explain your purpose clearly in tags(see Useful Tags), title, or content.
Group members will confirm the purpose of the issue, replace more accurate tags for it, identify related milestone, and assign developers working on it.
- Type: What kind of issue, e.g.
feature
,bug
,documentation
,performance
,support
...
support
: the issue asks helps from developers of our group. If you need helps to locate and handle problems or have any idea to improve Egnature, mark it assupport
.bug
: if you find a problem which possibly could be a bug, please tag it asbug
. Then our group members will review that issue. If it is confirmed as a bug by our group member, this issue will be tagged asconfirmed
.- A confirmed bug will be resolved prior.
- If the bug has negative impact on running online application, it will be tagged as
critical
, which refers to top priority, and will be fixed ASAP! - A bug will be fixed from lowest necessary version, e.g. A bug needs to be fixed from 0.9.x, then this issue will be tagged as
0.9
,0.10
,1.0
,1.1
, referring that the bug is required to be fixed in those versions.
All features must be submitted along with documentations. The documentations should satify several requirements.
- Documentations must clarify one or more aspects of the feature, depending on the nature of feature: what it is, why it happens and how it works.
- It's better to include a series of procedues to explain how to fix the problem. You are also encourgaed to provide simple, but self-explanatory demo.
- Please provide essential urls, such as application process, terminology explainations and references.
If you are developer of egnature repo and you are willing to contribute, feel free to create a new branch, finish your modification and submit a PR. Group will review your work and merge it to master branch.
# Create a new branch for development. The name of branch should be semantic, avoiding words like 'update' or 'tmp'. We suggest to use feature/xxx, if the modification is about to implement a new feature.
$ git checkout -b branch-name
# If your modification pass the tests, congratulations it's time to push your work back to us. Notice that the commit message should be wirtten in the following format.
$ git add . # git add -u to delete files
$ git commit -m "fix(role): role.use must xxx"
$ git push origin branch-name
Then you can create a Pull Request at Egnature
No one can guarantee how much will be remembered about certain PR after some time. To make sure we can easily recap what happened previously, please provide the following information in your PR.
- Need: What function you want to achieve (Generally, please point out which issue is related).
- Updating Reason: Different with issue. Briefly describe your reason and logic about why you need to make such modification.
- Related Testing: Briefly descirbe what part of testing is relevant to your modification.
- User Tips: Notice for Egnature users. You can skip this part, if the PR is not about update in API or potential compatibility problem.
You are encouraged to use angular commit-message-format to write commit message. In this way, we could have a more trackable history and an automatically generated changelog.
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
(1)type
Must be one of the following:
- feat: A new feature
- fix: A bug fix
- docs: Documentation-only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests
- chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
- deps: Updates about dependencies
(2)scope
The scope could be anything specifying place of the commit change. For example avatar-editor, dropzone etc...
(3)subject
Use succinct words to describe what did you do in the commit change.
(4)body
Feel free to add more content in the body, if you think subject is not self-explanatory enough, such as what it is the purpose or reasone of you commit.
(5)footer
- If the commit is a Breaking Change, please note it clearly in this part.
- related issues, like
Closes #1, Closes #2, #3
- If there is a change about an old feaure or a new feature, please associate
doc
andengature-core
, likeabhir9/Egnature-core#123
e.g.
fix($compile): [BREAKING_CHANGE] couple of unit tests for IE9
Older IEs serialize html uppercased, but IE9 does not...
Would be better to expect case insensitive, unfortunately jasmine does
not allow to user regexps for throw expectations.
Document change on abhir9/Egnature#123
Closes #392
BREAKING CHANGE:
Breaks foo.bar api, foo.baz should be used instead
Egnature uses semantic versioning in release process based on semver.
master
branch is the latest stable version. next
branch is the next stable version working in progress.
- All new features will be added into
master
ornext
branch as well as all bug-fix except security issues. In such way, we can motivate developers to update to the latest stable version. - If any API is discarded, it should be noted with
deprecate
in current stable version. The old version of API should be compatible until the release of next stable version. master
branch doesn't have publish tag. High-level framework can work with stable versions defined by semantic versioning.next
branch is labelled withnext
tag, high-level framework can useegnature@next
to test the in-progress version.- The LTS versions of Egnature determined by Milestone. If a version is listed in Milestone, then it is a LTS version. We will patch it if there is any problem with it.
In the release of every stable version, there will be a PM who has the following responsibilities in different stages of the release.
- Set up milestone. Confirm that request is related to milestone. Assign and update issues, like 1.x milestone.
- Create a
next
branch frommaster
branch and tag it asnext
.
- Confirm that performance test is passed and all issues in current Milestone are either closed or can be delayed to later versions.
- Open a new Release Proposal MR, and write
History
as node CHANGELOG. Don't forget to correct content in documentation which is related to the releasing version. Commits can be generated automatically.$ npm run commits
- Nominate PM for next stable version.
- Back up the stable version (master) onto the branch named after the current major (e.g:
1.x
), and set the tag torelease-{v}.x
(v is the current version likerelease-1.x
). - Push the
next
branch tomaster
, make it to the last stable one and removenext
tag, change the contents corresponding to the branch in README. - Publish the latest stable version to npm, and notify the previous framework to be upgraded.
- Before doing
npm publish
, please read How to deploy an npm package.
All tags mentioned above means the tags of npm in package.json
.
"publishConfig": {
"tag": "next"
}