Public SourceMage Discussion List

[Thomas Orgis <thomas-forum AT orgis.org>]

Am Sat, 28 Feb 2015 20:32:27 +0300
schrieb Vlad Glagolev <stealth AT tiberian.ru>: 

> Well, I have more than one hundred smgl servers, and no, I do not want
> to break everything because of yet-another-forced-and-not-compatible
> upgrade of A through Z.

Hm, so what you're really aiming at is to have some mental safety that
`scribe update` only pulls in security patches and not actually changes
anything that needs babysitting? A long term support grimoire?

My point was that other extreme: That between grimoire releases, so
many changes accumulate, that it's a bumpy path to upgrade.

I don't want to forgo a conclusion of the discussion. When we settle on
an approach that mandates stuff in test grimoire (master branch) not
being knowingly broken while not shying away from upgrades, and then
branch off that in some given interval stable grimpoires that are kept
stable for some extended time period, I'd be fine with that. Heck, you
can go down to one release per year, even, in that case. We'd also have
to think about supporting the "oldstable" with security fixes for some
period after the new one arrived. Because … server admins don't want to
do upgrades right away;-) On my development machine(s), I use the
grimoire right from git anyway.

It just seems like this is a change from what SMGL used to aim for, so
it should be communicated and agreed upon as such.

But getting current stable actually current can be done first, right?


Alrighty then,

Thomas

Attachment: pgpHEf2UbzG6c.pgp
Description: Digitale Signatur von OpenPGP