Yup.
Even though K2 has been stable and in a sense feature complete for a very long time, a 1.0 release has yet to happen. That’s about to change. That’s right, the temperature is dropping rapidly in hell, crafty engineer pigs are working on wings and propulsion systems and the US war efforts have seize… Two out of three isn’t bad.
I’ve gone through all the new issues in the issues database over the last few weeks and updated most of the ones that were floating around unassigned. Many of the open bugs have already been fixed, but there is still a substantial list of issues in need of more information from the reporters.
Beyond that, if you know of any issues, large or small, that aren’t already in the issues list, please take a minute to let us know so we can figure out what to do with it in relation to 1.0. In an effort to get the 1.0 happening sooner rather than later, I may be somewhat brutal in assigning new issues to the 1.1 milestone, but that doesn’t mean they won’t be dealt with. However, as you may have noticed, K2 development has a tendency to happen in short concentrated sprints. This is one, and if you want something noticed and fixed, now is a good time.
Check out the changelog for recent changes, grab the latest nightly and take it for a spin.
For our brave and tireless translators. I love you. But more than that, I hope you can find the time to update your localizations for 1.0. In return, my promise is that for 1.1 one of the main pushes will be to get the localizations into the trunk and support them with an easy language selector from the options page (also known as issue #793).
As usual, you can use the support group for communications and the localization home to upload your .pot files.
