[Filoret]

Does someone know how to autoupdate snapshot version of SM\MM? for example once at day

[berni]

Why would someone like to do this ?

Snapshot builds are not stable, if a build is is not working properly your server will be broken after the update.

[psychonic]

Originally Posted by berni Snapshot builds are not stable.

[Afronanny]

Originally Posted by psychonic

stable
stable
stable
stable

[berni]

I'm sorry then, I thought snapshots are not stable, even tho it's the stable branch.

Still I would like to know the reason for daily autoupdating.

[amohanlall32]

Perhaps to prevent "falling behind" on the latest SourceMod versions. Some people only come here once a year...or when valve breaks shit...lol

[Dr. McKay]

Originally Posted by psychonic

Didn't I get yelled at by you for saying that snapshots are stable? Or was it asherkin or someone...

Edit: found it.

[asherkin]

Both branches are meant to be stable (in terms of non-crashyness) overall, as changes with issues are backed out as soon as they're noticed.

This still leaves one or more built snapshots with any issues, as a new one is built every time a change is committed (or really, every time the tree is stable, that is, x amount of time has passed since the last commit).
For this reason, auto-updating to every build snapshot is a rather bad idea.

The stable/unstable titles of the two branches refers to the API, not crashyness.

It works like this:
API breaking changes, changes to stuff only in the unstable branch already, or changes that have a high likelihood to cause issues go in the unstable branch (at least initially), everything else goes in both.
As feedback is received, more changes are made, or previous ones are backed out if problematic and it can't be immediately fixed.
Before a release, the stable branch is semi-frozen, only changes that are fixes or have a near-0 chance of breaking anything are allowed to be added.
When a release is made, the version number get's changed in the repository, when the snapshot resulting from that is built it's packed with a few supporting files and released as a primary download, then the version number get's incremented and the -dev tag added back, creating the first snapshot of the next release.

The 3 conflicting definitions of "stable" in this post are intentional, as you'll find it used to mean all 3 all over the place, and it helps to emphasise the point.

[berni]

intended stable != stable

Originally Posted by psychonic That was a poor choice of wording, or rather, lack of clarification. The snapshots from the current stable branch, as labeled on the snapshots page, are intended to be stable. But as I've said in other posts, I recommend staying on release versions unless you are experiencing a specific issue that you know was fixed in a snapshot or if you intend on testing new features from the development branch.

Originally Posted by Afronanny stable stable stable stable

hah,
you can call a cat a "dog", but it will still be a cat