Ensure users know what is happening with updated versions coming down the pipes #55

New Issue

decentral1se · 2021-04-02T15:19:54Z

decentral1se commented

2021-04-02 15:19:54 +00:00

Now that we'll have the generation script publishing the versions (see https://git.autonomic.zone/coop-cloud/abra/issues/121), we will have to deal packagers publishing versions.

Some of those versions will be straight upgrades of the app service. Then users know what is coming for them. However, some of those will be updates to the underlying services and then the version tags add a ~<n> to them.

Taking Gitea for example, if we upgrade the database with a major version, we'd publish this new version 1.13.4~1 but that doesn't quite show that it is potentially breaking change.

So, one way to mitigate this will be to use CHANGELOG.md files in the app repos. Another way is to explain exactly what is going on via https://docs.cloud.autonomic.zone/packager-guide/#how-apps-are-versioned. And the other way is to make sure abra shows what versions are being deployed when an update goes out.

Leaving this open to track the implementation of these thoughts.

Now that we'll have the generation script publishing the versions (see https://git.autonomic.zone/coop-cloud/abra/issues/121), we will have to deal packagers publishing versions. Some of those versions will be straight upgrades of the `app` service. Then users know what is coming for them. However, some of those will be updates to the underlying services and then the version tags add a `~<n>` to them. Taking Gitea for example, if we upgrade the database with a major version, we'd publish this new version `1.13.4~1` but that doesn't quite show that it is potentially breaking change. So, one way to mitigate this will be to use `CHANGELOG.md` files in the app repos. Another way is to explain exactly what is going on via https://docs.cloud.autonomic.zone/packager-guide/#how-apps-are-versioned. And the other way is to make sure `abra` shows what versions are being deployed when an update goes out. Leaving this open to track the implementation of these thoughts.

decentral1se added this to the (deleted) milestone 2021-04-02 15:19:54 +00:00

decentral1se added the

enhancement

label 2021-04-02 15:19:54 +00:00

decentral1se referenced this issue

2021-04-07 12:45:09 +00:00

How to communicate config/underyling service changes using the n+1 naming scheme #58

decentral1se commented

2021-04-07 12:45:22 +00:00

Let's converge on https://git.autonomic.zone/coop-cloud/organising/issues/58 (more specific).

decentral1se closed this issue

2021-04-07 12:45:22 +00:00