Re: Changes - Part 2: Rolling Release Cycle
 

Sourcemod stable isn't catching or throwing an error related to that. Instead of terminating the execution chain, it crashes the server with no error log. Getting the native feature status helps, for plugins which call the native; but, doesn't fix the actual plugin owning the native getting updated.
https://crash.limetech.org/dm4nfwy3xbla

Re: Changes - Part 2: Rolling Release Cycle
 

That doesn't look related to any aforementioned changes. If you can reproduce the crash please file a bug @ https://bugs.alliedmods.net/

Re: Changes - Part 2: Rolling Release Cycle
 

Can the builds page show the build date?

Re: Changes - Part 2: Rolling Release Cycle
 

It already kinda does. Hover over the build number.

Re: Changes - Part 2: Rolling Release Cycle
 

Im on a mobile device. That would explain why i couldn't see it

Re: Changes - Part 2: Rolling Release Cycle
 

Anther Issue I have with this system is, things making it to the stable branch aren't really as tested and polished as they should be. There is no intermediate stage, as things go from development to stable. This was the case before switching to a rolling release; which, essentially made the problem worse by removing beta.

I find myself going back and finding an previous .smx binary under 1.6.4, because something major like function arguments aren't functioning properly after recompiling under 1.7.2. It's virtually impossible to diagnose this issue because the compiler just passes through flawlessly and the wrong errors appears to be happening in error logs.

In my opinion, the entire 1.7 branch is in more of a beta state than anything else. This is demonstrated by all the bugs getting fixed in the aftermath; And is detrimental to certain people who need constant stability.

Re: Changes - Part 2: Rolling Release Cycle
 

As has been said hundreds of times now, the "stable" and "dev" labels are to do with API stability and nothing to do with bugs or issues - both branches are "stable" in the sense that all known issues are fixed ASAP and if they can't be the changes that caused them are backed out.

Re: Changes - Part 2: Rolling Release Cycle
 

All binaries compiled before 1.7 are compatible with 1.7 and later, with the exception of a few that are doing things they shouldn't have been (specifically relating to datapacks). Being unable to compile a pre-1.7 plugin using the 1.7 compiler is another matter entirely.

Re: Changes - Part 2: Rolling Release Cycle
 

this bug? - changes last github commits not show in main page snapshots, and links.

Re: Changes - Part 2: Rolling Release Cycle
 

I noticed that too. My first thought it that they were just gamedata updates, but they still have descriptions on Github, so...

Re: Changes - Part 2: Rolling Release Cycle
 

This is fixed now. The process that updates that data for the web page was stuck.

Re: Changes - Part 2: Rolling Release Cycle
 

Can I expect metamod to also come at a rolling release cycle "soon" or not for a few months?

Re: Changes - Part 2: Rolling Release Cycle
 

The current plan is for MM:S to continue as-is.

Re: Changes - Part 2: Rolling Release Cycle
 

Ok thanks!

Re: Changes - Part 2: Rolling Release Cycle
 

Can we get a URL that always returns the latest release?

Re: Changes - Part 2: Rolling Release Cycle
 

http://www.sourcemod.net/downloads.php?branch=stable

Re: Changes - Part 2: Rolling Release Cycle
 

I believe what he's asking for is something like http://www.sourcemod.net/downloads.php/latest.<zip|tar.gz> which will immediately download the latest release.

If so, here's psychonic's reply to that: https://forums.alliedmods.net/showpo...2&postcount=17

Re: Changes - Part 2: Rolling Release Cycle
 

That sucks. Would be much easier to auto update SM once in a while.

Re: Changes - Part 2: Rolling Release Cycle
 

Code from https://github.com/easy-wi/developer...pdates.sh#L164

Re: Changes - Part 2: Rolling Release Cycle
 

Please don't scrape the downloads page. If you must scrape a file listing, use the "smdrop" directory listing, http://www.sourcemod.net/smdrop/1.7/ http://www.sourcemod.net/smdrop/1.8/

Re: Changes - Part 2: Rolling Release Cycle
 

Here's how you can download the latest version from smdrop without dependencies like lynx.
At least that's the way it's currently done in the calladmin project.

I'm no perl guy but looking at the way the files are packaged and uploaded it looks like you could either rename the package after it has been uploaded and upload that too or create two packages and upload both. What am i missing?

Re: Changes - Part 2: Rolling Release Cycle
 

I never knew that existed. Thanks!

Re: Changes - Part 2: Rolling Release Cycle
 

That would certainly work, but is a bit hacky. You'd wind up having a static filename, like sourcemod-1.8.0-latest and not know exactly what build you've downloaded.

When I said it was complex, I was referring to having a dynamic web link that would redirect to the latest download file (with untouched filename, including the build number).

I'm still not completely sold on the idea of having a programmatic way to download the latest build as I believe you should know what you're downloading, not just grabbing it because it's new. Regardless, it's very clear that it's a feature people want and are just going to scrape the downloads page or file list to get it if not provided another solution. I'll try to have something implemented this week.

Re: Changes - Part 2: Rolling Release Cycle
 

You should take that as a measurement of how much trust we put on you SM devs.

Re: Changes - Part 2: Rolling Release Cycle
 

It's more of a measurement of it not being feasible to test every change against every supported game on every supported OS.

Re: Changes - Part 2: Rolling Release Cycle
 

This has been added now. It's not documented anywhere yet, but I'll add a note on the downloads page tomorrow.

http://sourcemod.net/latest.php?os=<os>&version=<majorVersion>

Valid OS strings are: windows, linux, mac
Valid versions at time of writing are: 1.7, 1.8

Re: Changes - Part 2: Rolling Release Cycle
 

Am I going insane, or have the linux downloads at https://www.sourcemod.net/downloads.php all become archives of archives? The windows & mac ones seem fine.

Re: Changes - Part 2: Rolling Release Cycle
 

Can you link a specific one? I spot-checked a few and they seem to be fine - a single tarball, compressed with gzip.

Re: Changes - Part 2: Rolling Release Cycle
 

Hmm, you're right. 7Zip seemed to have issues with .tar.gz files for me I suppose. That with the latest links on the smdrop page not being the archives, but the latest filenames had me all confused.

Re: Changes - Part 2: Rolling Release Cycle
 

Yes, that's how 7-zip handles tarballs. It opens the outer .gz, which contains a .tar.

Re: Changes - Part 2: Rolling Release Cycle
 

Yes, I wish it had smarter handling of that like WinRar does.

Re: Changes - Part 2: Rolling Release Cycle
 

Great change details :P

Re: Changes - Part 2: Rolling Release Cycle
 

I am also like this update. This is very easier for people to work with game server.