Replies: 2 comments
-
I guess the correct title should be "How to complete AzerothCore" without 3.0. We need to release 3.0 and squash all the pending DB updates because the last time we did it was already more than 1 year ago. All the above ideas are of course nice, but I don't think we can complete it in a reasonable amount of time. |
Beta Was this translation helpful? Give feedback.
-
3.0 means: major release -> something that breaks old changes. I would like to stop versioning things in wrong way and keeping trace of PRs/changes that are fixing (patch), adding features (minor), rewriting without legacy support (major) In this case should a database squash considered a major version? what does it break? If you think so we can decide to proceed in that way otherwise we should use something like 2.5 instead |
Beta Was this translation helpful? Give feedback.
-
How to complete AzerothCore 3.0
As many of you noticed, most of the mangos-based servers are using the strategy of defining themself "unfinished-software".
The main reason is that such software are constantly a work-in-progress to fix bugs and implement new features at the same time that eventually generate more bugs and everything on the same branch.
The road to a real stable version
Semver:
DONE: To do a step forward AzerothCore adopted the Semver project versioning standard from the beginning: https://www.azerothcore.org/wiki/Project-Versioning
TODO:
Important NOTE: The Semver will help us to keep the compatibility with the ecosystem that we're creating. So it's very important to start using it in the correct way.
Documentation
DONE: Our wiki is the single-source-of-truth of all our server documentation: https://www.azerothcore.org/wiki/home . It's based on git and full of articles, however, it's just the beginning!
TODO:
Testing
Maybe the most important part! if we want to complete the AzerothCore-Wotlk product and be sure that the quality of the project is preserved during the time, the testing layer is the ONLY solution (I'll explain it to you why at the end of this post).
TODO:
Personal considerations about testing and its importance:
AzerothCore is not a simple application that can be unit-tested out of the box... it's a huge modular framework to create distributed servers, moreover, it comes with a very complex and large database. However, more and more private communities rely on the fact that open-source projects are not properly fixed, so you can't compete with them. So you need a "leek" or someone like the old "Sunwell" project who suddenly decided to release their hard job.
But that's not what normally happens on open-source projects...
For instance: You don't rely on closed source Oracle DB because MySQL DB is a bugged open-source project. You rely on Oracle DB because it offers some custom/premium features and good customer support. That is exactly what every private project should offer instead and what makes you better than others.
To do it we need more contributors! So, please, join our guild: azerothcore/forum#102 ! We need to expand our team
Beta Was this translation helpful? Give feedback.
All reactions