Skip to content

CHANGELOG.md: add v0.0.2 and v0.0.1 changes #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kolyshkin wants to merge 1 commit into from
Closed

CHANGELOG.md: add v0.0.2 and v0.0.1 changes #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 37 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
# Changelog
Copy link
Member

@AkihiroSuda AkihiroSuda Apr 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we even need to maintain CHANGELOG.md?
GitHub Releases have release notes

Copy link
Contributor Author

@kolyshkin kolyshkin Apr 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but I'd like the information to be accessible locally. Maybe it's not worth it, I dunno.

Copy link
Member

@thaJeztah thaJeztah Apr 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I was considering the same. While a change-log can be nice, it also easily gets forgotten to be updated, or adds additional maintenance.

For a project that produces binaries (such as runc), I could see it being more relevant (also for potential inclusion in deb, rpm packages), but a bit on the fence for a library module like cgroups

Copy link
Contributor Author

@kolyshkin kolyshkin Apr 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This kind of make sense. We can maintain the changelog under https://github.com/opencontainers/cgroups/releases


This file documents all notable changes made to this project since it was
split out of runc repository.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

[Unreleased]: https://github.com/opencontainers/cgroups/compare/v0.0.2...HEAD

## [0.0.2] - 2005-04-25

### Added
* CPU burst stats. (#11)
* CI infrastructure. (#3, #6)
* CI: add nolintlint linter. (#10)

### Changed
* Mark some fields with `omitempty` JSON attribute. (#9)
* Modernize code by using new Go features. (#13)
* CI: switch to golangci-lint v2. (#12)

### Fixed
* systemd: write rounded CPU quota to cgroupfs. (#4)

[0.0.2]: https://github.com/opencontainers/cgroups/compare/v0.0.1...v0.0.2

## 0.0.1 - 2025-02-28

### Added

* This is an initial release of the code after splitting it from the runc repository,
according to the [proposal].

[proposal]: https://github.com/opencontainers/tob/blob/main/proposals/cgroups.md