As you all know from the Resolutions & Expectations thread, this year we'll be facing things more directly and trying to address most of the issues that have hindered us so far. To start with our plans, let me introduce you the Codename "Tharros", our first Bug Tracker Operation of 2016, which is also, the first public one.
- One of the pillars of leadership, courage is what we need the most when facing challenging goals, be it at work, games or our lives.
The courage to innovate and try new things. The courage to accept our mistakes and try to improve them. To execute tasks and accomplish things.
It's the one virtue that makes all the others possible - it's our motion force.
Thárros (θάρρος) is the Greek word for Courage and has been chosen to name this Operation as it is a reflection of what we'll be needing the most this year - the courage to get down to business and say "let's do it" and regardless of the outcome, whether our goals are met or not, we'll be doing our best
- Bug Tracker Operations are hosted whenever we see the need of a mass engagement required in order to put things in place and clear the flow, so developers can address issues easier and the bugtracker reflects the exact current development status of our server.
The first Bug Tracker Operation was held a year and half ago and it had as goal the proper sorting of bug tracker issues, which were until that point pretty much neglected. And then at that time we were beating -100 unlabeled issues per day, undoubtedly, a lot of work. I believe at that time we had Chasity coordinating things and the testers assisting us, and they did most of the work with the assistance of some staff members and few players. The thread has rested for long at the Testing Territory section, but I think it's fine to share it now in case anyone is curious: viewtopic.php?f=66&t=13527&start=15
This is the first one planned for this year and is expected to last throughout this first semester.
- As said previously, this BTO has very challenging goals. Before getting ot them, let's first analyze our current summary of issues:
As can be seen, we have 729 Confirmed issues. From our starting point, we consider all of these confirmed issues as valid issues that eventually need to be looked into and fixed. However, there's one major issue in it - the maintenance of such issues.
As you all know, we're receiving updates weekly from our emulator's team (trinitycore) and from our developers, which puts us in a state of constant changes. Sometimes we win, sometimes we lose but that's expected. The problem is, in this state of constant changes, it's not possible for us to keep every report up to date and unfortunately some reports end up getting neglected. This creates false numbers - it makes it look like there are more issues than there actually are and hinders the effectiveness of our developers, that often get stumbled on things that are already working but still pending as bugged.
So now we get to our goals:
- Feedback Issues: 0 Issues
- Show no mercy to the issues labeled as Feedback. Feedback issues are often issues that either have already received a fix or have a developer working into them and require further confirmation. They should be the issues we exterminate firstly. If there's a fix applied at the Public Test Realm and it needs to be restarted or the software needs to be compiled you can always contact me and I'll see that it gets done, but overall, let's not give these issues any excuses to lie around - they're our main target!
Our goal is to have 0 Feedback issues.
Confirmed Issues: ~350 Issues
- Confirmed issues are the ones in greater quantity. As said previously, they're always considered as valid at our default approach. However, we're aware that there are many who've been fixed and may still be confirmed and it should be our goal to update those. Reducing the number of confirmed issues is the main goal of this Operation, even though they receive lower priority than Feedback labeled isues.
Our goal is to lower the current number of confirmed issues by half in this first semester of 2016. And woah... that IS a lot of work, and we'll never be able to accomplish that alone, so we really need the help of everyone willing to help with this
As you can see, there's a lot of work to be done and once again: we cannot do it alone. It'll take a lot of effort from our community to accomplish it, but surely we can do our best to accomplish it. Regardless of the outcome, whether we reach or not the goals set, this will be large improvement to our server, so even if we don't clear the issues we'd have already done something great for ourselves.
Helping: How To
- There are many ways you can contribute towards this, but at first you can start with:
- - Test your own issues. Any issue 1 month old is worth of being retested.
- Don't spam issues if they have already been retested by multiple people, you can contribute more if you look into an issue that hasn't been retested yet.
- Try to provide useful information to issues
- Soon you'll be able to request issue status updates at our Archon page (Nyeriah's pet project to support bug tracker activities and perhaps replace the tracker, if it ever manages to be that powerful).
- Players that show outstanding activity during this BTO will be chosen to participate in the Execution Phase of the "Ascension" promotional campaign. The closer we get to our goals, the more participants will be chosen. It's expected for the list of rewarded players to be released sometime at March. Further information is to be released within the next days.
AMA - Ask Me Anything
- Feel free to use this thread to ask me anything you'd like to ask about this Operation, the previous and the future ones or anything related to this initiative. I'll be answering your questions at the best of my capabilities.