<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">You should subscribe to the RSS feed at <a href="http://wordpress.org/news/category/releases/" target="_blank">http://wordpress.org/news/category/releases/</a>.<br>
</blockquote><div><br>You are changing mind :) <a href="http://lists.automattic.com/pipermail/wp-polyglots/2010-June/004672.html">http://lists.automattic.com/pipermail/wp-polyglots/2010-June/004672.html</a> :<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
<pre>I don't see a reason to develop a notification service other<br>than us manually sending an email as we are prepping everything for release.<br></pre></blockquote></div><br>Problem with relying on RSS from <a href="http://wp.org/news">wp.org/news</a> is that it is very slow process. We need faster notification via email.<br>
<br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">Demetris emailed this list 19 days ago, and we haven't changed a string
since. I also alerted the list to string changes as they occurred. Your
translations should be complete; you only need to push a button now.<br></blockquote><div> </div>You first need to know how this process works:<br>- we need to check if there is any new string since last update and if files for direct translation were changed<br>
- we commit translations to SVN and need to wait around 10 minutes before we can build a locale package at locale site<br>- we need to wait xx minutes before locale version will appear on upgrade screen even if it was hours before last check to api was made (I just tested this again today: I didn't have notification about update until I went to upgrade screen where I only got option to update to en_US even though locale package was already available on <a href="http://locale.wp.org">locale.wp.org</a>)<br>
- if we updated to en_US while there wasn't locale package, we will again receive notification about new version, this time with option to upgrade to locale package<br><br>So even if we have ready translations and see news about release the same moment as it is posted, we still need xx minutes before new locale version will appear at upgrade screen. And what if we don't release a locale package for several hours or day(s) because we were offline, unaware that new version will be released? Users will update to en_US, some strings will be untranslated (depending if it is version from new branch and how many changes there are in new version), and when new locale version is release they'll again get notification about update and they'll ask "WTF!? I already updated to this version!" <br>
<br>We need a different process related to releases. Translators should be warned when new version will be released, not just because they need to update translations, but because they need to be ready to "push a button" (if it was that simple). I could understand if there was need for unplanned release because of discovery of huge security issue that needs to be fixed as soon as possible, but those releases are not that often and you don't have a reason to not inform us in advance.<br>
<br>You must be aware that this process is not friendly for translators and for users of locale versions. You must be aware that there are users who use locale version (check for stats for exact percent) and you can't ignore that fact in release process. If you really want to fully support i18n and l10n in automatic upgrades and notification about upgrades, you must stop with current practice and make strict rules with translators about release process which should be followed by everyone.<br>
<br><div class="gmail_quote">2010/7/30 Andrew Nacin <span dir="ltr"><<a href="mailto:wp@andrewnacin.com">wp@andrewnacin.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
3.0.1 has been released.<div><br></div><div>I had an email drafted to polyglots, but we made a last minute change and I got sidetracked.</div><div><br></div><div>It hasn't been several hours; WordPress 3.0.1 proper was released 72 minutes ago, but I digress. You should subscribe to the RSS feed at <a href="http://wordpress.org/news/category/releases/" target="_blank">http://wordpress.org/news/category/releases/</a>.</div>
<div><br></div><div>Cheers!</div><div><br></div><div><font color="#888888">Nacin</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Thu, Jul 29, 2010 at 7:04 PM, Milan Dinić <span dir="ltr"><<a href="mailto:liste@srpski.biz" target="_blank">liste@srpski.biz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Again no notification in advance (I mean at least several hours) and no notification after release is made (so we still need to use external notification services).<br>
<br>I would expect that Nacin would inform us, he was active on this list last months.<br>
<br><div class="gmail_quote">2010/7/10 Demetris <span dir="ltr"><<a href="mailto:kikizas@gmail.com" target="_blank">kikizas@gmail.com</a>></span><div><div></div><div><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello, polyglots!<br>
<br>
This is a note that WordPress 3.0.1 is expected to be released around mid July.<br>
<br>
Like all maintenance releases, it will be a very good opportunity for<br>
translation teams to push improvements/additions/corrections/etc. in<br>
their localizations.<br>
<br>
(I know that I try to take advantage of maintenance releases for that<br>
purpose—fixing strings, localizing more strings, etc.—, and I imagine<br>
other WordPress translators do the same thing.)<br>
<br>
Note also that 3.0.1 has a few changes in strings (mainly to correct<br>
typos, if I remember correctly). So, remember to update your PO files<br>
too!<br>
<br>
Cheers,<br>
<font color="#888888"><br>
Demetris<br>
<a href="http://op111.net/76" target="_blank">http://op111.net/76</a> ‹ See what is new in WordPress 3.0!<br>
_______________________________________________<br>
wp-polyglots mailing list<br>
<a href="mailto:wp-polyglots@lists.automattic.com" target="_blank">wp-polyglots@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>
</font></blockquote></div></div></div><br>
<br>_______________________________________________<br>
wp-polyglots mailing list<br>
<a href="mailto:wp-polyglots@lists.automattic.com" target="_blank">wp-polyglots@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>
<br></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
wp-polyglots mailing list<br>
<a href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-polyglots" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a><br>
<br></blockquote></div><br>