diff options
author | Matthias Beyer <mail@beyermatthias.de> | 2018-02-11 15:14:52 +0100 |
---|---|---|
committer | Matthias Beyer <mail@beyermatthias.de> | 2018-02-11 15:16:42 +0100 |
commit | 07f2182120ee4f451491a98fe72b60c01d0ec73f (patch) | |
tree | b94ea00b84a7759fd8e796766e985e6d53c6e7bf | |
parent | d5b8020f08a8b61ca4b60fabe5922227f3b009bb (diff) |
Add post: imag 0.6.1
-rw-r--r-- | content/blog/2018-02-11-imag-0-6-1.md | 53 |
1 files changed, 53 insertions, 0 deletions
diff --git a/content/blog/2018-02-11-imag-0-6-1.md b/content/blog/2018-02-11-imag-0-6-1.md new file mode 100644 index 0000000..7fd7478 --- /dev/null +++ b/content/blog/2018-02-11-imag-0-6-1.md @@ -0,0 +1,53 @@ +--- +title: "imag 0.6.1" +slug: "imag-0-6-1" +date: "2018-02-11T13:22:06" +tags: [ "linux", " open source", " programming", " rust", " software", " tools", " imag" ] +--- + +imag 0.6.1 is a bugfix release which fixes two severe bugs in `imag-init`: + +* `imag-init` created the git repository inside the imag directory. But it + really should be created in `{imag directory}/.git`. This was fixed. +* `imag-init` was buggy as it did not include the `imagrc.toml` file in the + release, thus building it from crates.io failed. + +Only `imag-init` was published, all other crates remain in `0.6.0` (rationale +read below). + +# On publishing patch releases + +I thought that I won't release patch-releases before 1.0.0 of imag, but this +is too severe to _not_ be fixed as soon as possible. + +Hence I created the "v0.6.x" branch where the most critical bugfixes will be +backported. +I will not, though, republish all crates for each patchlevel release (like I do +with each 0.y.0 release). +I will only publish the fixed crate or all affected crates. +So if there happens to be a critical bug in `libimagstore` and I want to +publish a fixed release for this, I will publish all crates with a new +patchrelease, but if there is a bug in `imag-store`, I will only republish +`imag-store` with the fix. + +What I will _not_ do, though, is increment the patchlevel for all crates +independently. +The fixed crates will be increased to the new number. Thus, I am releasing +`imag-init` in `0.6.1` now. If there is a bug in `imag-entry` I need to fix, I +will release it as `0.6.2` then. +This is mainly because of the git tags but also because everything else is +ugly. +I don't want to create a `0.6.1-init` or `0.6.1-imag-init` tag for the bugfix +release and later a `0.6.1-entry` or `0.6.1-imag-entry` tag. +I simply increase the number with each bugfix release. + +One policy I learned from the kernel community which I want to apply in imag +as well: A bugfix is backported to the `v0.6.x` branch _only if_ it is already +included in `master`. +With this, we ensure that bugs are the two branches do not diverge too much. + +Changelog updates will be merged back to master by cherry-picking them. + +Lets hope 0.6.1 is the first and the last bugfix release for the 0.6.x series! +:-) + |