|
1 | 1 | Changelog
|
2 | 2 | =========
|
3 | 3 |
|
| 4 | +Release Cycle |
| 5 | +------------- |
| 6 | + |
| 7 | +Prior to v1, the version numbers loosely followed the rule that new features |
| 8 | +would bump the minor version level, and bug fix releases would bump the patch |
| 9 | +version level. |
| 10 | + |
| 11 | +Beginning with v1, a new scheme is adopted which allows for a "development" |
| 12 | +version, and a stable version. Using the version numbers `x.y.z`, we have: |
| 13 | + |
| 14 | +1. The **development** version is of the form `x.0.z`, where `x` represents the |
| 15 | + major version under development. Each release is performed by incrementing |
| 16 | + `z`, the patch level, regardless of the type of changes. The development |
| 17 | + version ends with the release of the "stable" version of `x.1.0`. The |
| 18 | + development version is maintained on the `main` branch. |
| 19 | +2. The **stable** version is of the form `x.y.z`, where `y >= 1`, and `x` is of |
| 20 | + course the major version. The "stable" versions are the only ones which are |
| 21 | + released to Oracle Linux as RPMs. Releases will generally increment `z`, the |
| 22 | + patch version, for bug fix releases. It's possible that in rare cases, we |
| 23 | + will increment `y` for backports, in cases where we want to backport a module |
| 24 | + to the stable release. The stable version is maintained in a branch named |
| 25 | + `stable/vX`, where `X` is replaced with the major version number (e.g. |
| 26 | + `stable/v1`). |
| 27 | + |
| 28 | +The stable version is maintained in parallel as the development version is |
| 29 | +developed. Fixes in the stable release must first be present in the development |
| 30 | +release (and all newer stable releases, if applicable). |
| 31 | + |
| 32 | +For the most part, regular maintenance of the stable version will end with the |
| 33 | +release of the next stable version, but maintenance may continue at our |
| 34 | +discretion. |
| 35 | + |
| 36 | +Examples: |
| 37 | + |
| 38 | +- `1.1.0` - the initial public release of the `1.x` stable series. |
| 39 | +- `1.1.1` - the first bugfix release of the `1.x` stable series. |
| 40 | +- `2.0.0` - the initial development version of the `2.x`. |
| 41 | +- `2.0.1` - an incremental development release in `2.x` development. It may |
| 42 | + contain bug fixes or new features. |
| 43 | +- `2.1.0` - the initial public release of the `2.x` stable series. |
| 44 | + |
| 45 | + |
4 | 46 | Unreleased
|
5 | 47 | ----------
|
6 | 48 |
|
7 | 49 | Changes which are committed to git, but not yet released, may appear here.
|
8 | 50 |
|
| 51 | +1.1.0 - Tue, Aug 27, 2023 |
| 52 | +------------------------- |
| 53 | + |
| 54 | +This is the first public release of drgn-tools! |
| 55 | + |
| 56 | +* Fixes for the irq, workqueue, bt, & nfs_tools modules. |
| 57 | +* Add ls and fsnotify modules. |
| 58 | +* Added new helpers for tasks & task states. |
| 59 | +* Basic functionality for running on UEK-NEXT (unsupported). |
| 60 | +* RPM name updated to "drgn-tools". |
| 61 | +* Support for CTF debuginfo added for the locks module. |
| 62 | + |
9 | 63 | 0.9.1 - Mon, Apr 22, 2023
|
10 | 64 | -------------------------
|
11 | 65 |
|
|
0 commit comments