Wikka Developer Blog

We are planning to build a base of official testers for WikkaWiki, this post is to announce the launch of our beta-testing programme and the availability of (unstable) nightly builds from our code repository.

Joining the Wikka Beta-Testing programme

WikkaWiki is a popular solution for LAMP servers, but how does it perform in other environments? We welcome beta-tester applications from users running Wikka on less represented environments (e.g. IIS, lighttpd) and/or with different PHP/MySQL versions.

The ideal beta tester is familiar with the inner workings of Wikka, s/he doesn’t need to be a programmer but should be able to help us identify bugs and issues with specific components and report them in the tracker. Communication between the Dev Team and beta testers will take place on #wikka or via the community mailing list.

What are the benefits of joining our beta testing programme? You will be the first to try the newest features of Wikka, you will be able to propose improvements and discuss direct code changes to the engine with the developers and enjoy the pleasure (?) of spotting unseen bugs before they make it to the end user. Beta testers will be publicly acknowledged in the Wikka Dev Team page.

If you wish to apply as a beta tester drop us a line on the community list or visit #wikka.

Nightly builds for the masses

On a related note, Brian has recently setup a nightly builds script to package and deliver to your doorstep the freshest unstable version of Wikka. So far development versions of the engine were only available to users familiar with SVN. You can now download and install unstable releases to get a taste of what’s going on in the main development line. As Brian puts it:

“Unstable” releases represent the cutting edge of Wikka development. Sometimes referred to as the “trunk” version (because this represents the main SVN version from which all other releases are derived), these releases are automatically built nightly and include all changes and updates that have been made by the Wikka devs up to that point. While every effort is made to ensure the “trunk” version runs properly, there are no guarantees that all features are fully implemented and ready for prime time. Consequently, do not use unstable releases in a production or mission-critical environment! We do, however, encourage feedback from those who have the time and resources to run these releases.

Thanks for helping make Wikka better and stronger!