Kopano community upgrade to supported version.

thctlo

Hai,

The version numbering of kopano community and supported version are different.
Which give problem when you want to upgrade from communtie to supported.

apt-cache policy kopano-server
kopano-server:
Installed: 8.5.81.288-0+53.1
Candidate: 8.5.81.288-0+53.1
Version table:
*** 8.5.81.288-0+53.1 100
100 /var/lib/dpkg/status
8.5.8.2-0+27.1 500
500 https://download.kopano.io/supported/core:/final/Debian_9.0 Packages

no, this look “almost” ok but it it not.
8.5.81.288-0+53.1 100 around 15 Feb 2018
8.5.8.2-0+27.1 500 just release.

Is this intended? because the community version is updated daily?
This make imo, things more confusing.

Just a thing i noticed.

Greetz,

Louis

jengelh

when you want to upgrade from communtie to supported.

Technically, that is a downgrade (similar to Linux distributions), since “supported” has an older code base compared to “community”. The version numbers reflect that. The frequency of updates of either of the two is unrelated to that.

thctlo

Hai,
Yes, technically it is yes, agree, but this these are both in the “8.5” line. I especialy waited for this moment.

The supported version is a CVE release and should have upgrade the communty version, which was not updated since 15 Feb in my personal repo.

So in this case, i wanted to stay on the 8,5 version because … for example, i wanted to test/prepair to to a “supported or paid” verion for kopano…
Then you end up in a problem. Thats good to know…

8.5.81.288-0+53.1
8.5.8 .2 -0+27.1 500

This is asking for problems imo, in the long run, and wil scare people if you want to switch between versions

thctlo

Just a suggestion, all "beta: aka communty releases,
i would suggest, 8.5.0-0.xx -… 8.5.1-0.xx -… 8.5.2-0.xx -…
and where you can make the following if you want.
0.1xxxx alpa release
0.5xxxx beta release
0.9xxxx pre-release
1.00 final release.

now if this one hits supported, it should get 8.5.0-1.xx-… 8.5.1-1.xx-… 8.5.2-1.xx-… 8.5.3-1.xx-…
The next CVE would be 8.5.0-2.xx-… and the devs increase the .xx numbers.

This makes it always upgradable but just a suggestion, think about it.

fbartels

Hi @thctlo ,

thanks for your suggestion. Our current version schema is as follows:

8.6.80 - master/nightly builds
8.6.90 (until 8.6.99) - beta and RC builds for the next release (including branching to a release branch) this also marks the moment where the master builds get incremented to the next major.
8.7.0 - first final release of the 8.7 branch

The cve updates you were asking about were also released with the latest noghtlies, so there is no need to “stay with 8.5.x”.

If you want to prepare an upgrade to a supported version we/sales are happy to help you out with an evaluation key, so you directly install the supported versions.

thctlo

Hai Felix,
I totaly understand what your saying, but think about this.
Ow and… i have a contributed license, that why i posting a lot, im contributing…

I’m a communtiy version user and i want to upgrade to the paid version. … fail 8.6 upgrade to 8.5?
lets try again.
I’m a communtiy version user and i want to upgrade to the contribtion version. … fail 8.6 upgrade to 8.5?

You get my point?

Can you explain why this is even possible.

8.5.81.288-0+53.1 community version d.d. 15 Feb 2018
8.5.8.2 -0+27.1 500 contributed version d.d. 23 Apr 2018

it this a typo in the 5.8.8.2 version which should be 8.5.82 ?
That would explain it.

fbartels

@thctlo said in Kopano community upgrade to supported version.:

I’m a communtiy version user and i want to upgrade to the paid version. … fail 8.6 upgrade to 8.5?

Why “fail”? As Jan already said when going from community to supported this is a downgrade. A simple procedure, not a big problem.

@thctlo said in Kopano community upgrade to supported version.:

Can you explain why this is even possible.

8.5.81.288-0+53.1 community version d.d. 15 Feb 2018
8.5.8.2 -0+27.1 500 contributed version d.d. 23 Apr 2018

it this a typo in the 5.8.8.2 version which should be 8.5.82 ?

As explained above the community version numbering is oriented to the next mayor version. From the moment there is a branch for the next major release (8.5.x) the community versioning switches to the next major (current community versions are 8.6.80 if I’m not mistaken). Community versions leading to the 8.5 release were 8.4.90 for example.

thctlo

why fail… one example, community 8.6 has for example kopano-spamd
contributed, supported and paid are one version down, … without kopano-spamd. so i say fail.
but thats my opionion.

i’ll keep reporting my findings, what you guys do with them is up 2 you.

fbartels

@thctlo said in Kopano community upgrade to supported version.:

community 8.6 has for example kopano-spamd

You could also install the 8.6 packages from pre-final. They have spamd included as well.

thctlo

Hai,
https://documentation.kopano.io/kopanocore_administrator_manual/introduction.html

2.3. Components does not mention kopano spamd.

externa1

You’ll find it under 6.11

https://documentation.kopano.io/kopanocore_administrator_manual/special_kc_configurations.html#configuring-kopano-spamd-for-automatic-spam-ham-learning

rg
Christian