Changes - Part 2: Rolling Release Cycle
 

SourceMod is now officially on a rolling release cycle.

What this means to you
There won't be any more "point" releases (1.7.3, etc). Instead, we're going to continue to make an effort to keep the stable branch stable, and better relay information about what has changed in each build.

Major releases with potential API breakage will still occur and will still have release notes, along with continued updates even after the branch is considered to be stable.

The old Downloads and Snapshots pages on the SourceMod website have been merged and now contain more useful information than before. There are immediate links at the top to download the latest build for your OS, as well as other recent builds displayed below with information about the changes in that build over the previous one.

Additionally, all builds (formerly referred to as snapshots) include full localization data as well as updated Geo-IP data, just like previous release versions.

We're still sorting out some small things, but most everything is in place now. If you come across any issues with these changes, please post a comment in this thread.

Re: Changes - Part 2: Rolling Release Cycle
 

Excellent! The most important part for me was knowing the changes from the releases and snapshots. Now it's right there.

Re: Changes - Part 2: Rolling Release Cycle
 

This change should make it easier for people to get the correct SM version to work with a game server

Re: Changes - Part 2: Rolling Release Cycle
 

Nice job, this is much cleaner than the older system plus people can know when a major crash bug is fixed if a game like TF2 updates faster, neat.

Re: Changes - Part 2: Rolling Release Cycle
 

Will MetaMod: Source be moved over to rolling releases as well?

Also a word to the wise: FindMap's syntax changed between the Stable (1.7) and Unstable (1.8) builds:

There's a compatibility shim in place to make code that uses FindMap compiled under 1.7 work in 1.8, but you can't compile code that uses the older syntax with the current unstable/development compiler.

Edit: This wasn't relevant before as FindMap appeared in 1.7.3, but since it's now part of the "release" Stable version, now it is relevant.

Re: Changes - Part 2: Rolling Release Cycle
 

I appreciate the change, but man - the OS icons are awful. Why don't use flat desing to match other parts of the website?

Re: Changes - Part 2: Rolling Release Cycle
 

All signs point to yes.

Re: Changes - Part 2: Rolling Release Cycle
 

The page is functional, it hasn't had its sprinkle of pixel dust yet.
Unless you'd prefer to have had this delayed a few months just over the aesthetic of a couple of buttons?

Re: Changes - Part 2: Rolling Release Cycle
 

Naah, keep up the good work! :) I could help you with the icons, if you wish.

Re: Changes - Part 2: Rolling Release Cycle
 

I like this update, much easier that browsing through that waterfall page. I did like the waterfall page though because it showed when a build was being processed and time remaining. Will there be anything like that for compile times on this new page?

Re: Changes - Part 2: Rolling Release Cycle
 

Nice. Suggestions for new icons: Windows Linux Apple

Re: Changes - Part 2: Rolling Release Cycle
 

Those are the current icons.

Re: Changes - Part 2: Rolling Release Cycle
 

Oh... :shock: But it looks terrible with blue background.

Re: Changes - Part 2: Rolling Release Cycle
 

A sourcemod-1.7.3-latest-<os>.zip could be useful for automated scripts and so..

Re: Changes - Part 2: Rolling Release Cycle
 

All of the sourcemod plugins stopped working on my server today. I'm wondering if it has to do with this update.

EDIT: Derp, my server hosting website hasn't updated to the sourcemod version yet so I have to do it manually, I was running 1.7.2

Re: Changes - Part 2: Rolling Release Cycle
 

That or maybe some api-like thing that returns the url to the latest branch. I dislike using regex to filter it out .~.

and if we use the latest.zip, name it atleast sourcemod-stable-latest.zip.

Re: Changes - Part 2: Rolling Release Cycle
 

The existing waterfall URL still works. I just didn't find a good place for it on the new page yet.

I agree, and us already having that would have made that part of the page much easier to implement as well. However, it's not easy to cleanly add in our current setup. It's still on the list.

Re: Changes - Part 2: Rolling Release Cycle
 

@Akuba
You don't need regex for this. If you have access to a shell you can use something like this
You can see it being used by calladmin here. It's not perfect but it works for now.

Re: Changes - Part 2: Rolling Release Cycle
 

Empty languages.cfg in build 5241.

Re: Changes - Part 2: Rolling Release Cycle
 

I was looking for something like this, thank you :D

Re: Changes - Part 2: Rolling Release Cycle
 

Thanks for reporting. Despite it working fine in testing, there were some other considerations that needed to be handled for the actual build machines. This should be fixed a bit later today.

Re: Changes - Part 2: Rolling Release Cycle
 

Can you have a page where it displays the URL to the latest SM build in VDF or XML form so that automatic updaters can just check that page for the newest version?

Like someone else said, using regex isn't exactly fun.

(Oh and do this for metamod too if you can.)

Re: Changes - Part 2: Rolling Release Cycle
 

The languages.cfg should now be fixed in the latest builds.

Re: Changes - Part 2: Rolling Release Cycle
 

It might be a good idea to put a note (if not a redirect) on the old downloads and snapshots pages. Google hasn't indexed the new download page(s) yet, so googling "sourcemod download" won't give you the right downloads.

Re: Changes - Part 2: Rolling Release Cycle
 

In addition to a -latest release, can there also be a release that just contains scripting files for developers who want to update their build environment? I'm finding it tiring to have to download the entire zip just to unpack compile.exe and include/ files.

Re: Changes - Part 2: Rolling Release Cycle
 

Yea same for leaving out particular plugins/translations.

Re: Changes - Part 2: Rolling Release Cycle
 

Is there a good way to verify the downloaded files? Previously you provided SHA1 and MD5 checksums, but I guess the safest way now is to download over HTTPS. Any plan to add back checksums?

Re: Changes - Part 2: Rolling Release Cycle
 

The previously provided checksums always required you to trust the path between sourcemod.net and your client and were entirely to guard against malicious mirror operators, they provide no benefit when downloading directly from sourcemod.net (so, yes, use HTTPS).

Re: Changes - Part 2: Rolling Release Cycle
 

Perhaps the changelog between multiple commits could be shown when they happen at the same time.

Something like this - http://i.imgur.com/cA8x9HK.png - or multiple lines on the same build row, whatever works!

Re: Changes - Part 2: Rolling Release Cycle
 

Speaking of which, setting convars using ConVar methodmaps is now working again in the latest release.

Re: Changes - Part 2: Rolling Release Cycle
 

Stable branch isn't very stable at all, if you're updating plugins with natives. :cry:

Re: Changes - Part 2: Rolling Release Cycle
 

Stable means no ABI breaks. ABI breaks are allowed on the development branch (and therefore it's recommended extension authors don't release binaries against it).

Re: Changes - Part 2: Rolling Release Cycle
 

Might want to fix that URL in the first post there: http://www.sourcemod.net/downloads.php?branch=stable

Re: Changes - Part 2: Rolling Release Cycle
 

Thanks. Fixed.

Re: Changes - Part 2: Rolling Release Cycle
 

spam my log

7/2015 - 12:48:08: SourceMod log file session started (file "L20150917.log") (Version "1.7.3-dev+5253")
L 09/17/2015 - 12:48:08: -------- Mapchange to zombiemonde_metro_v1b --------
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.l4d2.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.ep2valve.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.l4d.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.ep1.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.csgo.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.sdk2013.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.ep2.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.contagion.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.blade.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.swarm.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated gamedata file "core.games/engine.darkm.txt"
L 09/17/2015 - 12:48:12: [UPDATER] Successfully updated game

Re: Changes - Part 2: Rolling Release Cycle
 

You're welcome. We're happy to see you appreciate the data you're being fed up with.

(....or would you rather prefer functionality to break?)

Re: Changes - Part 2: Rolling Release Cycle
 

is normal?

Re: Changes - Part 2: Rolling Release Cycle
 

It should happen only the first time it detects new updated gamedata. Past that it shouldn't print that again (or so I hope it doesn't).

If SM doesn't update gamedata then it won't work AT ALL on your game (or it will but not properly).

Re: Changes - Part 2: Rolling Release Cycle
 

The gamedata updater will always replace all gamedata files from the first time a snapshot is installed.

The reason being that file line endings differ between the gamedata in snapshots and the gamedata the updater checks against, so the updater believes the files in the snapshot are outdated. It's essentially harmless.

Re: Changes - Part 2: Rolling Release Cycle
 

are there any important fixes in the new builds vs 1.7.2 for l4d and l4d2. i know other games require new sourcemod updates regurely.