Skip to content

Commit d6aa235

Browse files
committed
Prepare for the v0.1.0 release
Signed-off-by: Sahas Subramanian <sahas.subramanian@proton.me>
1 parent 9a39aea commit d6aa235

4 files changed

Lines changed: 83 additions & 1 deletion

File tree

.github/RELEASE_NOTES.template.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
# frequenz-microgrid-rs Release Notes
2+
3+
## Summary
4+
5+
<!-- Here goes a general summary of what this release is about -->
6+
7+
## Upgrading
8+
9+
<!-- Here goes notes on how to upgrade from previous versions, including deprecations and what they should be replaced with -->
10+
11+
## New Features
12+
13+
<!-- Here goes the main new features and examples or instructions on how to use them -->
14+
15+
## Bug Fixes
16+
17+
<!-- Here goes notable bug fixes that are worth a special mention or explanation -->

CONTRIBUTING.md

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Contributing to frequenz-microgrid-rs
2+
3+
## Releasing
4+
5+
These are the steps to create a new release:
6+
7+
1. Get the latest head you want to create a release from.
8+
9+
2. Update the version in `Cargo.toml` to the new version. Without this,
10+
the new release will be rejected by `crates.io`.
11+
12+
Along with this, update the `RELEASE_NOTES.md` file if it is not
13+
complete, up to date, and remove template comments (`<!-- ... ->`)
14+
and empty sections.
15+
16+
Submit a pull request if an update is needed, wait until it is
17+
merged, and update the latest head you want to create a release
18+
from to get the new merged pull request.
19+
20+
3. Create a new signed tag using the release notes and
21+
a [semver](https://semver.org/) compatible version number with a `v` prefix,
22+
for example:
23+
24+
```sh
25+
git tag -s --cleanup=whitespace -F RELEASE_NOTES.md v0.0.1
26+
```
27+
28+
4. Push the new tag.
29+
30+
5. A GitHub action will test the tag and if all goes well it will create
31+
a [GitHub
32+
Release](https://github.com/frequenz-floss/frequenz-microgrid-rs/releases),
33+
and upload a new package to
34+
[crates.io](https://crates.io/crates/frequenz-microgrid-rs)
35+
automatically.
36+
37+
6. Once this is done, reset the `RELEASE_NOTES.md` with the template:
38+
39+
```sh
40+
cp .github/RELEASE_NOTES.template.md RELEASE_NOTES.md
41+
```
42+
43+
Commit the new release notes and create a PR (this step should be automated
44+
eventually too).
45+
46+
7. Celebrate!

README.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,16 @@
11
# frequenz-microgrid-rs
2-
High-level interface for Rust to the Frequenz Microgrid API
2+
3+
[<img alt="docs.rs" src="https://img.shields.io/docsrs/frequenz-microgrid-rs">](https://docs.rs/frequenz-microgrid-rs)
4+
[<img alt="Crates.io" src="https://img.shields.io/crates/v/frequenz-microgrid-rs">](https://crates.io/crates/frequenz-microgrid-rs)
5+
6+
High-level interface for Rust to the Frequenz Microgrid API.
7+
8+
## Documentation
9+
10+
For more information, please visit the [documentation
11+
website](https://docs.rs/frequenz-microgrid-rs).
12+
13+
## Contributing
14+
15+
If you want to know how to build this project and contribute to it, please
16+
check out the [Contributing Guide](CONTRIBUTING.md).

RELEASE_NOTES.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# frequenz-microgrid-rs Release Notes
2+
3+
## Summary
4+
5+
This is the first release of `frequenz-microgrid-rs`.

0 commit comments

Comments
 (0)