On Friday last week, [Jokosher](https://www.jokosher.org/) hit its feature freeze. This means that no new features will enter Jokosher and the next month will be spent purely on bug-fixing. As some of you will know, there has actually been little major new functionality in Jokosher since 0.2 – this release is about bug-fixing and getting Jokosher streamlined, sanding off the edges and getting it stable.

Now, we need your help. We really, *really* do. We want Jokosher 0.9 (the next release, scheduled for a March release) to be rock-solid. We have a month scheduled for bug fixing, but we need to know your bugs. We need you folks to test it and report problems to us so we can fix them. Without lots of testing, Jokosher will simply not be stable enough. If we all work together, we will have a rock-solid Jokosher on our hands. 🙂

So how do you do this? Well, I have written a [simple little guide](https://userdocs.jokosher.org/TestingDevelopmentJokosher). Testing is a pretty simple process and requires no programming knowledge – it just means you test Jokosher and tell us when it screws up. So, go read [the guide](https://userdocs.jokosher.org/TestingDevelopmentJokosher) and help us test it and make it kick some arse.

We also have our [Jokosher Forums](https://www.jokosher.org/forums/) as a place to discuss the application and your experiences testing it. Specifically, the [Help Forum](https://www.jokosher.org/forums/viewforum.php?f=2) is useful for testing related discussion.

I am serious here – we *really*, **really** need your help testing Jokosher. It is critical that we get as many bug reports as possible about things that don’t work quite right so we can nail them for the next version, which will be making an appearance in most distros when it is released. Now is the time, *test it, report it, discuss it!*