How to download beta or final release

Hello,

I’am coming from Zarafa and just updated my server to Kopano 8.2 unstable.
I noticed a new beta version of 8.2 was released so I thought I update the server to this new beta 2 release.
However I cannot find the beta or final releases of the community version.
Only the current last build seems available through download.kopano.io.

Where can I download these releases?

Thanks,
Joep

You have to go to https://download.kopano.io/supported/ but thats only available with active subscription, for community only the Master Branch / Nightly Builds are available afaik

rg
Christian

Hi Joep,

What Christian said is correct. Some additional information about this can be found at https://kopano.com/how-to-get-kopano

I was afraid of that.

Don’t you want the community to test the upcoming releases?
Currently only 8.3 (master) is downloadable while 8.2 still has to be released.

Hi,

@joepadmiraal said in How to download beta or final release:

Don’t you want the community to test the upcoming releases?

Yes, and with the master build you always have the latest and greatest to test and play around with. I know that the release packages and master currently seem worlds apart, but we’ve already taken steps to make this gap smaller after the 8.2.0 final release.

@joepadmiraal said in How to download beta or final release:

I was afraid of that.

Don’t you want the community to test the upcoming releases?
Currently only 8.3 (master) is downloadable while 8.2 still has to be released.

I agree, this seems like a big benefit being lost for the commercial release. If the community had the release a week or two ahead of commercial, then there would be time to test. If there is only nightlies and no freeze, how is the final release tested for any length of time, or at all?

@scottalanmiller that depends on the branching model. We implement fixes in the “master” branch (from which the nightly releases are built). As point x everything in “master” is merged into “release” (to have a beta, rc, whatever) release. As soon as its ready to be declared as final it goes to “stable”.

We don’t merge anything into master, that is not intended for the next release.

@fbartels said in How to download beta or final release:

@scottalanmiller that depends on the branching model. We implement fixes in the “master” branch (from which the nightly releases are built). As point x everything in “master” is merged into “release” (to have a beta, rc, whatever) release. As soon as its ready to be declared as final it goes to “stable”.

That’s what I was assuming. But in that case, how long does anyone have on the final release before other changes are made to the nightlies? It means that the final fixes going into the final release have had only one day of time to be tried out, I assume. Not that those final changes would be big, I assume that they are tiny and the tiny ones before that had two days and the tiny ones before that had three days and so forth, but if there is something wrong in the final, they only test it thoroughly once released, I think.

@scottalanmiller who is “they” in your reply? Before releasing a beta or final for our subscription customers we internally do extensive tests for the distributions we have listed as supported.

@fbartels said in How to download beta or final release:

@scottalanmiller who is “they” in your reply? Before releasing a beta or final for our subscription customers we internally do extensive tests for the distributions we have listed as supported.

“They” was a reference to the nightly code changes. “They” (the nightly amount of new code added) are small. Sorry if that was a strange way to say that.