Testing Servers (Alpha and Beta)
Posted: 13 Jul 2011, 19:12
In an attempt to overcome many of the bug issues before they reach Platinum (aka server.themanaworld.org) we are attempting to establish several points of review. This effort is to put less stress on the server's administration and to put more responsibility in the tmwAthena development team. The end result should, hopefully, make content updates happen more smoothly on Platinum.
1. Establish testing repository clones - done
Though we've worked with testing repository clones of one type or another since I began my leadership of this project, it is worth noting that this is our first point of review. Commits to our -test clone repositories should be: Bug fixes, small alterations and small, finished, projects. For larger projects, a project developer can make a clone repository of our -test repositories in cooperation with the General Content Team. To keep these clones in check, a member from the General Content Team should have push access to the project clone repository and can review the project clone for if/when it is done.
When a project is finished, it can be merged onto the -test repositories. By "finished" it should be in its final form and at most, needs to be reviewed for bugs and copy-editing by the General Content Team collectively.
2. Establish an official alpha testing server - done (?)
The -test clone repositories are the repositories for the official testing server. Once our -test repos have been tested locally to ensure no major issues are being sent, we will update our testing server for public play-testing. We may have it operate with manual direct administration, remote administration and/or a script that will do automatic updates and restarts periodically. After the General Content Team confirms copy-editing to be complete and no bugs can be found both locally and through the testing server, we are ready to merge with the -data repository.
3. Establish an official stable beta clone server - not done
After a merge onto the -data repository, the content is almost ready for Platinum, but not quite. In an effort to ensure that the merge didn't create any major issues we will run an official stable beta server that is an exact clone of server.themanaworld.org. This stable server will not be just for testing purposes, but will operate as a true public server, capable of holding the interest of a small secondary player community. Though we'd think those that would play on such a server would be interested in play testing content before it reaches Platinum with permanent characters, there will be no overall guideline for how players should participate with this server in relation to development. We may give some benefit, such as running the content for a week on the beta server before it reaches Platinum, to encourage final testing.
The beta server may operate differently based on the administration the General Content Team decides on. Though all Platinum rules would apply, as it is an exact clone, interpretation may be different. All General Content Team members would have GM level 80 permissions, as would the server administrator. Further GMs would be decided on should an actual secondary player community exist on this server.
1. Establish testing repository clones - done
Though we've worked with testing repository clones of one type or another since I began my leadership of this project, it is worth noting that this is our first point of review. Commits to our -test clone repositories should be: Bug fixes, small alterations and small, finished, projects. For larger projects, a project developer can make a clone repository of our -test repositories in cooperation with the General Content Team. To keep these clones in check, a member from the General Content Team should have push access to the project clone repository and can review the project clone for if/when it is done.
When a project is finished, it can be merged onto the -test repositories. By "finished" it should be in its final form and at most, needs to be reviewed for bugs and copy-editing by the General Content Team collectively.
2. Establish an official alpha testing server - done (?)
The -test clone repositories are the repositories for the official testing server. Once our -test repos have been tested locally to ensure no major issues are being sent, we will update our testing server for public play-testing. We may have it operate with manual direct administration, remote administration and/or a script that will do automatic updates and restarts periodically. After the General Content Team confirms copy-editing to be complete and no bugs can be found both locally and through the testing server, we are ready to merge with the -data repository.
3. Establish an official stable beta clone server - not done
After a merge onto the -data repository, the content is almost ready for Platinum, but not quite. In an effort to ensure that the merge didn't create any major issues we will run an official stable beta server that is an exact clone of server.themanaworld.org. This stable server will not be just for testing purposes, but will operate as a true public server, capable of holding the interest of a small secondary player community. Though we'd think those that would play on such a server would be interested in play testing content before it reaches Platinum with permanent characters, there will be no overall guideline for how players should participate with this server in relation to development. We may give some benefit, such as running the content for a week on the beta server before it reaches Platinum, to encourage final testing.
The beta server may operate differently based on the administration the General Content Team decides on. Though all Platinum rules would apply, as it is an exact clone, interpretation may be different. All General Content Team members would have GM level 80 permissions, as would the server administrator. Further GMs would be decided on should an actual secondary player community exist on this server.
