Changes - Part 2: Rolling Release Cycle - Page 5

stickz · *Last edited by stickz; 09-20-2015 at 09:13.*

Quote:

Originally Posted by BAILOPAN

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).

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

BAILOPAN · 09-21-2015 , 03:44 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/

Neuro Toxin · 09-23-2015 , 18:03 Re: Changes - Part 2: Rolling Release Cycle

Can the builds page show the build date?

psychonic · 09-23-2015 , 20:28 Re: Changes - Part 2: Rolling Release Cycle

Quote:

Originally Posted by Neuro Toxin

Can the builds page show the build date?

It already kinda does. Hover over the build number.

Neuro Toxin · 09-23-2015 , 20:46 Re: Changes - Part 2: Rolling Release Cycle

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

stickz · *Last edited by stickz; 10-01-2015 at 15:53.*

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.

asherkin · 10-01-2015 , 16:10 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.

Dr. McKay · 10-01-2015 , 20:45 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.

Electr000999 · 10-08-2015 , 14:26 Re: Changes - Part 2: Rolling Release Cycle

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

Powerlord · 10-08-2015 , 14:34 Re: Changes - Part 2: Rolling Release Cycle

Quote:

Originally Posted by Electr000999

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

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