Raised This Month: $12 Target: $400
 3% 

Solved Is Amx 1.8.3 Stable?


  
 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
Arkshine
AMX Mod X Plugin Approver
Join Date: Oct 2005
Old 08-16-2017 , 14:26   Re: Is Amx 1.8.3 Stable?
Reply With Quote #13

Well, it's not that simple.

The next version is 1.9. It's a major version and it's expected to have a lot of changes. Though, the changelog is actually not that big. As I've probably said already, the goal is to make things more up-to-date because it's really needed, not to break things. To be honest, at the start, we were just trying to fix/improve things here and there and we ended with a fair share of internal & important changes because the more you dig in the code, the more you find real issues which need to be addressed.

A particular issue is we lack people (test/review), so the development is kind of slow. Sometimes everyone is busy/lazy for a while. Sometimes someone finds bugs and this can lead to a bunch of fixes/improvements/new stuff. Sometimes you want to update a plugin but you need to update the modules before. It can't be helped. Time flies fast. Believe me, sometimes it's really frustrating. The point is, before we knew, a lot of stuff was already merged. At this point, you can't just release an half-baked AMXX version. The next version became major, in the meaning, a lot of things everywhere have been touched. There is no real dramatic change. Full backward-compatibility is obviously kept, the dev version should perform better with the same behavior as the previous version, but we are human, we don't have enough feedbacks and sometimes a bug can pop up.

Actually, there are not much core/internal changes, some are enough important to involve a lot of code, but what is really big is the stuff for the developer, way too much, I agree and it's enough for this version. On the contrary, admin stuff has been kind of ignored. That's why, before we go in feature freeze state, I want at least update the plugins and offer some long-awaited features for admins, because each time they are ignored :P.

If you want to know the big plan is something like:

1) Finishing to write/format/check the release notes and API changes (this is quite the nightmare, I assure you), then posting on the wiki.
2) Making an announce we're still alive, some words about the next version, linking to the release notes, and asking some help (test/review/pr/etc).
3) Opening Issues tab on Github because everyone hates or doesn't know bugtracker.
4) Trying to update/add stuffs for admins.
5) Declaring the version is now feature freeze and maybe inviting more people to test the dev version.
6) After a while, preparing the release (doc, installer, translations, etc.)
7) Releasing finally the shit and dying in peace.
8) Announcing future release will be on a rolling cycle, like SourceMod, because it makes sense.
9) And after that, that would a great step.
__________________

Last edited by Arkshine; 08-16-2017 at 14:47.
Arkshine is offline
 


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 04:30.


Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
Theme made by Freecode