- If you notice something that should be fixed or could be improved, please create an issue. This could be related to the library or to documentation.
- Branch off of
master. - Name the branch something meaningful and short. Consider prefixing the branch name with
feature/,fix/, ordocs/to help clarify the area and scope of work. - Commit work to the branch.
- Add an appropriate copyright notice to source files, following the IU Open Source Guidelines.
- Explain the change in the affected
CHANGELOGfile, categorizing it as patch, minor, or major changes (following semver conventions). - Submit a pull request for the branch to be merged into
master. - Tag the pull request and related issues with the
Nextmilestone. - Mention any related issues in the pull request.
- Once the pull request is approved, merge it to
masterwith the Squash and merge setting. - Delete the original branch.
- Commit all work into master, including updating the version number in
package.json. - Ensure a publish date and the new version numbers are mentioned in the
CHANGELOGfiles. - Only what is in
masterwill be published. - Ensure the bundles are built.
npm run start - Use the Lerna wizard to confirm which packages should be published and what version numbers they will be bumped to. Each package can be versioned separately, and not all packages need to be published at once.
npm run publish - Confirm that the package is available through npm, the repo is tagged, and the packages have new version numbers.
- Rename the milestone from
Nextto whatever the published version number is. Give it a short, meaningful description. Close the milestone. - Create a new milestone called
Next.