mORMot Open Source

berocoder

Member

From: Nedervetil, Finland

Registered: 2017-01-13

Posts: 19

Stable vs latest

Hi, most software projects have a stable branch and releases.

Say I have a big software project and want to use mormot in that.
I just want it to work so I want a stable version. Latest (trunk) is maybe not the best choice then as it may have bugs not yet found during beta testing.
So what is the policy of Mormot ?

On https://synopse.info/fossil/wiki?name=Downloads

The now deprecated "stable" version (1.17) is currently outdated, and some issues are probably already fixed.
Before asking for support about a possible bug or a missing feature, you should better retrieve the latest trunk/unstable version directly from our source code repository.
Regression tests are run before any commit, so it is safe to use the 1.18 trunk revision, even if it is named "unstable" - it is in fact more stable than the main 1.17 version!

So basically the recommendation is to always use the latest trunk even in the production environment as there are automatic regression tests?
I don't agree. Such complex component needs a period of time for beta testing before it is considered stable.

Regards
Roland Bengtsson

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 14,659

Website

Re: Stable vs latest

You are not wrong.

This is why we take another direction with the upcoming mORMot 2.
It will use semantic versioning.
https://github.com/synopse/mORMot2

berocoder

Member

From: Nedervetil, Finland

Registered: 2017-01-13

Posts: 19

Re: Stable vs latest

Ok was not aware of that. But still curious why not use this kind of development earlier.

edwinsn

Member

Registered: 2010-07-02

Posts: 1,218

Re: Stable vs latest

curious why not use this kind of development earlier.

Every project has its own growing path

---

Delphi XE4 Pro on Windows 7 64bit.
Lazarus trunk built with fpcupdelux on Windows with cross-compile for Linux 64bit.