[unison-users] confusing versioning

[Björn Ketelaars [e-mail] [unison-users]]

I'm kind of confused by the versioning of unison:

Github states that the latest unison release is v2.51.2 [0], while the
homepage [1] has it listed as beta. Assuming that the homepage is
correct the latest stable release is 2.48.4 [2].

Any idea of one should remain on the 2.48.x branch for stable releases,
or switch to 2.51.x?

[0] https://github.com/bcpierce00/unison/releases
[1] http://www.seas.upenn.edu/~bcpierce/unison//download/releases/beta/
[2] http://www.seas.upenn.edu/~bcpierce/unison//download/releases/stable/

[Benjamin Pierce [e-mail] [unison-users]]

2.51.2 is still officially a beta release, but it is about to become the stable release in the next few days. That’s the one to use.

More generally, we should do something about the duplicate release sites situation. Probably simplest is just to use github for all releases in the future, if someone can point me to documentation on how to mark releases there as beta and later upgrade to stable.

- Benjamin

Post by Björn Ketelaars ***@hydroxide.nl [unison-users]
Github states that the latest unison release is v2.51.2 [0], while the
homepage [1] has it listed as beta. Assuming that the homepage is
correct the latest stable release is 2.48.4 [2].
Any idea of one should remain on the 2.48.x branch for stable releases,
or switch to 2.51.x?
[0] https://github.com/bcpierce00/unison/releases
[1] http://www.seas.upenn.edu/~bcpierce/unison//download/releases/beta/
[2] http://www.seas.upenn.edu/~bcpierce/unison//download/releases/stable/
--
Björn Ketelaars
GPG key: 0x4F0E5F21
------------------------------------
------------------------------------
------------------------------------
Yahoo Groups Links

[Alan Schmitt [e-mail] [unison-users]]

Post by Benjamin Pierce ***@cis.upenn.edu [unison-users]
More generally, we should do something about the duplicate release sites
situation. Probably simplest is just to use github for all releases in the
future, if someone can point me to documentation on how to mark releases there
as beta and later upgrade to stable.

There is a button at the bottom of the release edit page to say it's a
pre-release. This adds a red tag to the release. Is it good for you?
https://github.com/bcpierce00/unison/releases

Alan

['Benjamin C. Pierce' [e-mail] [unison-users]]

Perfect. So let’s just point here from the release page on the Unison web site?

Post by Alan Schmitt ***@polytechnique.org [unison-users]

Post by Benjamin Pierce ***@cis.upenn.edu [unison-users]
More generally, we should do something about the duplicate release sites
situation. Probably simplest is just to use github for all releases in the
future, if someone can point me to documentation on how to mark releases there
as beta and later upgrade to stable.

There is a button at the bottom of the release edit page to say it's a
pre-release. This adds a red tag to the release. Is it good for you?
https://github.com/bcpierce00/unison/releases
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-12: 406.82, 2016-12: 404.42

[Alan Schmitt [e-mail] [unison-users]]

Post by 'Benjamin C. Pierce' ***@cis.upenn.edu [unison-users]
Perfect. So let’s just point here from the release page on the Unison web site?

Yes, I thinks it's the simplest and most consistent approach.

Alan