In short: As a head beta tester it is your responsibility to maintain the beta team and ensure each update is bug free.
Maintain the beta team
You must ensure that there is an active beta team for developers at all times. If a developer requires some testing, you must ensure there is always somebody on IRC to assist. You must also scout for potential beta team members and recruit any you think are appropriate and mature enough.
Organise beta tests
There will always be a roadmap stickied on these forums showing the current plans. This will include release dates. You must monitor this roadmap and ensure that every new feature has been tested excessively and is bug free before we release. You will also have access to the trac so you can monitor tickets. It is suggested that a weekly beta test is organised. For example, every Sunday and Wednesday at 6pm.
Write tickets[b]
If you find a bug, it will be your responsibility to write a ticket on the trac for it.
[b]Write blog posts
If a developer is to busy, it may be necessary for you to write a blog post. This should not be hard because ideally you should have tested everything ingame already so should have a fair idea of what's new. You'll also have access to the changelog on the wiki.
Requirements
* Trac account
* Access to LVPs development channel
* Access to LVPs development board
* Wiki account
* Moderator privileges on the beta boards
* Moderator access to the beta team group
You will also get a say on new features when we're making new roadmaps.
Maintain the beta team
You must ensure that there is an active beta team for developers at all times. If a developer requires some testing, you must ensure there is always somebody on IRC to assist. You must also scout for potential beta team members and recruit any you think are appropriate and mature enough.
Organise beta tests
There will always be a roadmap stickied on these forums showing the current plans. This will include release dates. You must monitor this roadmap and ensure that every new feature has been tested excessively and is bug free before we release. You will also have access to the trac so you can monitor tickets. It is suggested that a weekly beta test is organised. For example, every Sunday and Wednesday at 6pm.
Write tickets[b]
If you find a bug, it will be your responsibility to write a ticket on the trac for it.
[b]Write blog posts
If a developer is to busy, it may be necessary for you to write a blog post. This should not be hard because ideally you should have tested everything ingame already so should have a fair idea of what's new. You'll also have access to the changelog on the wiki.
Requirements
* Trac account
* Access to LVPs development channel
* Access to LVPs development board
* Wiki account
* Moderator privileges on the beta boards
* Moderator access to the beta team group
You will also get a say on new features when we're making new roadmaps.