(Migrated) Zato 1.2 stability

(This message has been automatically imported from the retired mailing list)

Hi,

We plan to start a Zato project very soon and put it into production 1. Mar=
ch.

We are considering which version to use - 1.1 or 1.2 dev. I think that seve=
ral things point towards 1.2 dev. But is it stable enough at this point for=
production use?

Regards,

Finn Gruwier Larsen

Forbrugerr?det Taenk er en uafhaengig medlemsorganisation, der arbejder for=
et Danmark, hvor alle forbrugere kan traeffe et trygt valg.
F? nyheder, informationer om test, tilbud og gode r?d 1-2 gange om ugen. Ti=
lmeld dig vores nyhedsbreve p? taenk.dk/nyhedsbrev

On 01/16/2014 11:16 AM, Finn Gruwier Larsen wrote:

We plan to start a Zato project very soon and put it into production 1. March.

We are considering which version to use - 1.1 or 1.2 dev. I think that several things point towards 1.2 dev. But is it stable enough at this point for production use?

Hi Finn,

the version in git master is fairly stable in the sense that it will
work but it’s not guaranteed that there won’t be backward-incompatible
changes.

Let’s consider a couple of scenarios.

  • You pick a commit 123

  • A feature is being developed in a feature branch

  • The features consists of code changes mostly unrelated to the code in
    master

  • The feature is done and applied cleanly into master using ‘merge
    –no-ff’ so you have clear information that something bigger was added

  • You can just take it an use it

  • You pick a commit 123

  • A feature is being developed in a feature branch

  • The feature consists to a great extent of new services and updates to
    existing ones, including their SQL tables

  • ‘merge --no-ff’ is used again

  • Here, you won’t have any instructions how to proceed next - how to
    upgrade the database or migrate data. This is a development version, not
    a frozen one.

So this is how it looks like. You need to understand it that this code
is stable, yet not frozen. So anything you possibly stumble upon will be
fixed yet there’s no guarantee it won’t change, and to what extent if it
does.

On 01/16/2014 11:16 AM, Finn Gruwier Larsen wrote:

We plan to start a Zato project very soon and put it into production 1. March.

We are considering which version to use - 1.1 or 1.2 dev. I think that several things point towards 1.2 dev. But is it stable enough at this point for production use?

Hi Finn,

the version in git master is fairly stable in the sense that it will
work but it’s not guaranteed that there won’t be backward-incompatible
changes.

Let’s consider a couple of scenarios.

  • You pick a commit 123

  • A feature is being developed in a feature branch

  • The features consists of code changes mostly unrelated to the code in
    master

  • The feature is done and applied cleanly into master using ‘merge
    –no-ff’ so you have clear information that something bigger was added

  • You can just take it an use it

  • You pick a commit 123

  • A feature is being developed in a feature branch

  • The feature consists to a great extent of new services and updates to
    existing ones, including their SQL tables

  • ‘merge --no-ff’ is used again

  • Here, you won’t have any instructions how to proceed next - how to
    upgrade the database or migrate data. This is a development version, not
    a frozen one.

So this is how it looks like. You need to understand it that this code
is stable, yet not frozen. So anything you possibly stumble upon will be
fixed yet there’s no guarantee it won’t change, and to what extent if it
does.