mORMot Open Source

edwinsn

Member

Registered: 2010-07-02

Posts: 1,215

Mark "recommended to upgrade" github revisions?

Arnaud,

I'm not sure if it makes sense, but obviously you are aware that mORMot is being actively developed (https://github.com/synopse/mORMot/commits/master), sometimes a commit is for bugfixes while another is for new functions, and it's not feasible to keep updated on a daily basis.

May I suggest you to distinguish the revisions by categories, for example, "for beta test only", "considered stable", "new function in progress", etc? That'll help us to decide which revision to use for production.

Have a nice weekend!

---

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

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 14,207

Website

Re: Mark "recommended to upgrade" github revisions?

It may be time to make an official release of the 1.18.

But most of the time, you could use any release, once all regression tests do pass for them.

The latest versions are almost always more stable.
Regressions are found very fast, usually.

So what you can do is use a version, test it on your side, then if there is no regression signaled in the TimeLine after one or two weeks, you can use it on production.

But of course, you have regression tests for your app, so it is not a problem to update your production environment, right?

At least, you may use a "pre-production" test environment, either at your main office, or with a sub-part of your customers.

edwinsn

Member

Registered: 2010-07-02

Posts: 1,215

Re: Mark "recommended to upgrade" github revisions?

Thanks for your reply. You are right. And now if I think a little bit more about it, actually your commit comments are informative enough to identify which rev. to use.

---

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