Demand: Release notes for Kopano community edition

There is only one unstable (nightly) Kopano community edition available. There are no release notes available for the changes in the nightly builds.

I am using Kopano for private purposes only and i am updating to the latest build on a weekly basis. Half of the time i am running into several problems after upgrading wich leads the system down. It’s horrible for every administrator to troubleshoot failed upgrades without having relase notes or without knowing what changed.

Release notes are in my opinion mandatory, even for open source software.

I have the following suggestions:

  • Publish release notes for every build.

  • Establish a “dev” channel wich is likely unstable and a more stable “release candidate” channel. Maybe there are only release notes for the “release candidate”.

Looking forward to an answer.

Regards
Richard

Hello Richard,

since KC-303 a changelog should be included in the packages themselves, apart from that there is a RELNOTES.txt in the root of each branch.

To get a more in depth look of all the changes, you can also have a look into the commit history.

Hi Felix,

the release notes in the root of each branch belong to the related minor release (8.1.0, 8.2.0, 8.3.0,…). The same applies for the changelogs in /usr/share/doc/kopano-common.

Should the “nightly release notes” be already included in the DEB packages?

Regards
Richard

If a change is merged into its related branch, then RHELNOTES is updated as well. You can see this in https://stash.kopano.io/projects/KC/repos/kopanocore/commits/5b3411c4b2bece4aba93290feb91e88b553a08da#RELNOTES.txt

Hi Felix,

let me give you an example:

I just upgraded from version 8.3.0, 534 to version 8.3.0, 560. Where is the place to view the changes made between those versions?

Regards
Richard

Hello Richard,

you can get this information from the git commit history. See https://stash.kopano.io/projects/KC/repos/kopanocore/commits for more information.

Hi Felix,

not very pretty but better than nothing. A changelog like commented in the last post in KC-303 would be very nice, but books like that’s only implemented for RPM based packages. Is this planned for DEB based packages too?

Regards
Richard

I try to install myself the latest releases really just to help Kopano to move forward and find issues if I can.

The trouble right now is that I have to install the package, then work out what has changed or perhaps whether I should have installed it or not

Personally I think rather then in the package there should be a text file or something available with the JIRAs that have been closed and that we can inspect for that build online.

This is a lot more effective… you can work out what changed and which JIRAs were committed and then if you find a strange behaviour you can refer back.

I am really just trying to help here.