Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/micro-os-plus/build-helper-xpack
A source code project with scripts and other files to support builds
https://github.com/micro-os-plus/build-helper-xpack
Last synced: about 2 months ago
JSON representation
A source code project with scripts and other files to support builds
- Host: GitHub
- URL: https://github.com/micro-os-plus/build-helper-xpack
- Owner: micro-os-plus
- License: mit
- Created: 2021-01-20T12:04:11.000Z (about 4 years ago)
- Default Branch: xpack
- Last Pushed: 2024-11-21T09:25:26.000Z (2 months ago)
- Last Synced: 2024-11-21T10:25:42.602Z (2 months ago)
- Language: CMake
- Homepage:
- Size: 431 KB
- Stars: 0
- Watchers: 3
- Forks: 1
- Open Issues: 3
-
Metadata Files:
- Readme: README-MAINTAINER.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
[![license](https://img.shields.io/github/license/micro-os-plus/build-helper-xpack)](https://github.com/micro-os-plus/build-helper-xpack/blob/xpack/LICENSE)
[![GitHub issues](https://img.shields.io/github/issues/micro-os-plus/build-helper-xpack.svg)](https://github.com/micro-os-plus/build-helper-xpack/issues/)
[![GitHub pulls](https://img.shields.io/github/issues-pr/micro-os-plus/build-helper-xpack.svg)](https://github.com/micro-os-plus/build-helper-xpack/pulls)# Maintainer info
## Project repository
The project is hosted on GitHub:
-
To clone the stable branch (`xpack`), run the following commands in a
terminal (on Windows use the _Git Bash_ console):```sh
rm -rf ~/Work/micro-os-plus/build-helper-xpack.git && \
mkdir -p ~/Work/micro-os-plus && \
git clone \
https://github.com/micro-os-plus/build-helper-xpack.git \
~/Work/micro-os-plus/build-helper-xpack.git
```For development purposes, clone the `xpack-develop` branch:
```sh
rm -rf ~/Work/micro-os-plus/build-helper-xpack.git && \
mkdir -p ~/Work/micro-os-plus && \
git clone \
--branch xpack-develop \
https://github.com/micro-os-plus/build-helper-xpack.git \
~/Work/micro-os-plus/build-helper-xpack.git
```To link it to the central xPack store:
```sh
xpm link -C ~/Work/micro-os-plus/build-helper-xpack.git
```## Prerequisites
A recent [xpm](https://xpack.github.io/xpm/), which is a portable
[Node.js](https://nodejs.org/) command line application.## How to make new releases
### Release schedule
There are no fixed releases.
### Check Git
In the `micro-os-plus/build-helper` Git repo:
- switch to the `xpack-develop` branch
- if needed, merge the `xpack` branchNo need to add a tag here, it'll be added when the release is created.
### Increase the version
Update the`package.json` file; add an extra field in the
pre-release field, and initially also add `.pre`,
for example `2.14.0-pre.1`.### Fix possible open issues
Check GitHub issues and pull requests:
-
and fix them; assign them to a milestone (like `2.14.0`).
### Update `README-MAINTAINER.md`
Update the following files to reflect the changes
related to the new version:- `README-MAINTAINER.md`
- `README.md`### Update `CHANGELOG.md`
- open the `CHANGELOG.md` file
- check if all previous fixed issues are in
- add a new entry like _* v2.14.0_
- commit with a message like _prepare v2.14.0_### Push changes
- commit and push
### Commit the new version
- select the `xpack-develop` branch
- commit all changes
- `npm pack` and check the content of the archive, which should list
only `package.json`, `README.md`, `LICENSE`, `CHANGELOG.md`,
the `doxygen-awesome-*.js` and `doxygen-custom/*` files;
possibly adjust `.npmignore`
- `npm version patch`, `npm version minor`, `npm version major`
- push the `xpack-develop` branch to GitHub
- the `postversion` npm script should also update tags via `git push origin --tags`
- wait for the CI job to complete
()## Publish to npmjs.com
- `npm publish --tag next` (use `npm publish --access public` when
publishing for the first time)The version is visible at:
-
## Test
Test the package.
## Update the repo
When the package is considered stable:
- with a Git client (VS Code is fine)
- merge `xpack-develop` into `xpack`
- push to GitHub
- select `xpack-develop`## Tag the npm package as `latest`
When the release is considered stable, promote it as `latest`:
- `npm dist-tag ls @micro-os-plus/build-helper`
- `npm dist-tag add @micro-os-plus/[email protected] latest`
- `npm dist-tag ls @micro-os-plus/build-helper`