We’ve recently published the documentation for some of the APIs that have been introduced in 2.0 but had not been covered in the manual at all. If you are a Zabbix expert, you’re probably already aware of their existence, but if you don’t know your way around the source code, you might have missed them. Anyway, you can now familiarize yourself with six useful APIs for maintaining your Zabbix configuration. Continue reading “Newly documented APIs”
When we started following the string freeze principle for Zabbix 2.0.3 release, the goal was to give translators some time period before each release, thus increasing the chances of a translation being completely finished. That did help, and 2.0.3 came out with 6 translations at 100%. Now the translation freeze for Zabbix 2.0.5 starts.
“Why on earth was I not notified?!” — ever heard that question from a fellow worker? Setting up notifications can be a challenge — and not only for beginners. Normally, debugging such cases is cumbersome, complex and requires a good understanding of how Zabbix works. Were you ever asked for a list of people who would be notified on some event? It’s hard to tell, until the event actually happens. Or at least it used to:
The Action Simulator tries to relieve you from these problems and make you and your co-workers happy again.
Update: Presenting the Action simulator at the Zabbix Conference 2013
EPEL finally offers Zabbix 2.0 packages. These packages are for you, if you are running RHEL, CentOS, Scientific Linux or any other Red Hat derivative. EPEL aims to provide best quality packages, that follow the same rules and conventions as Red Hat packages and therefore integrate smoothly.
The 2.0.4 release contains a lot of improvements so one tiny change may have passed unnoticed: the version of the API has been bumped to 2.0.4 as well. Indeed, that’s one small change in the code, but a huge decision for the Zabbix developers team. The API version has remained on 1.4 since the release of 2.0, but finally we’ve developed a versioning that will suite our needs. Continue reading “API versioning”
As announced two months ago, translation/string freeze is obeyed now. Zabbix 2.0 branch enters freeze now in preparation for 2.0.4 release.
For 2.0.3 our awesome translators managed to get 6 translations to 100%. How will it go for 2.0.4?
Zabbix is translated in multiple languages, 21 in total. Some are in better shape, some in worse, but the 2.0.3 release marks something fairly unique – 6 languages have 100% coverage.
The Zabbix conference welcoming event is as soon as tomorrow. Here at the Zabbix office we are having some fresh decorations – and a whole bunch of community members 🙂
The translation improvement initiative is progressing nicely. We had a large jump for French from 69% to 100% and Japanese did the last sprint from 98% to 100% as well. The last percent for Chinese (Taiwan) was finished even before that, thus there are currently 5 translations that are 100% finished. Hooray!
Another significant improvement was German, going from 81% to 94%, and Ukrainian went from 79% to 87%.
Still some 8 hours left to get the translations in 2.0.3. While large surprises are less likely to happen now, let’s see whether there will be any other noticeable improvements.
As many already know, Zabbix is translated in many languages, better in some, worse in others. With all the improvements that have happened to the translation framework and processes, including moving to gettext and recent introduction of string freeze, it seems like a good time to set some goals. How about getting as many translations as possible to 100% for 2.0.3?