I'm upgrading some code I wrote to talk to a new version of the Citrix
NetScaler's API. The
NetScaler's manuals (that's right, plural) weigh in at a combined 1114 pages so
documentation isn't a problem and their implementation is a breeze using WSDL over SOAP. However, some of the core changes left me
scratching my head. Case in point:
I'll be in Morocco at the end of next week and noticed there wasn't a single
Mozilla Party in the country! There were
over 36,000 download
pledges though, so there must be Firefox supporters somewhere. :)
Adding context to the .po files on AMO has been one of our challenges since
we started localizing the site. The solution we decided to use, place
holder strings, is non-standard and can be difficult to use for someone that
is used to how gettext normally works.
I've been the lead of the AMO 3.4.x
development release cycles which have been going on for about 8 weeks. During
that time we've been a little more structured with our release schedule. The
general plan has been a code freeze every other Monday at midnight and a push to
production the following Thursday. This gives us roughly ten days of coding and
two days of QA and L10n for each push. It's a compromise but it means
that we're never too far away from bug fixes and new features. The short turn
around cycle also means there aren't dramatic changes which lead to confusion
and panic (I'm looking at you mozillaZine ;) ).