[wp-polyglots] WordPress 3.0.1 expected around mid July

[Milan Dinić]

>
> You should subscribe to the RSS feed at
> http://wordpress.org/news/category/releases/.
>

You are changing mind :)
http://lists.automattic.com/pipermail/wp-polyglots/2010-June/004672.html :

I don't see a reason to develop a notification service other
> than us manually sending an email as we are prepping everything for release.
>
>
Problem with relying on RSS from wp.org/news is that it is very slow
process. We need faster notification via email.

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.
>

You first need to know how this process works:
- we need to check if there is any new string since last update and if files
for direct translation were changed
- we commit translations to SVN and need to wait around 10 minutes before we
can build a locale package at locale site
- 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 locale.wp.org)
- 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

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!"

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.

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.

2010/7/30 Andrew Nacin <wp at andrewnacin.com>

> 3.0.1 has been released.
>
> I had an email drafted to polyglots, but we made a last minute change and I
> got sidetracked.
>
> 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
> http://wordpress.org/news/category/releases/.
>
> Cheers!
>
> Nacin
>
>
> On Thu, Jul 29, 2010 at 7:04 PM, Milan Dinić <liste at srpski.biz> wrote:
>
>> 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).
>>
>> I would expect that Nacin would inform us, he was active on this list last
>> months.
>>
>> 2010/7/10 Demetris <kikizas at gmail.com>
>>
>> Hello, polyglots!
>>>
>>> This is a note that WordPress 3.0.1 is expected to be released around mid
>>> July.
>>>
>>> Like all maintenance releases, it will be a very good opportunity for
>>> translation teams to push improvements/additions/corrections/etc. in
>>> their localizations.
>>>
>>> (I know that I try to take advantage of maintenance releases for that
>>> purpose—fixing strings, localizing more strings, etc.—, and I imagine
>>> other WordPress translators do the same thing.)
>>>
>>> Note also that 3.0.1 has a few changes in strings (mainly to correct
>>> typos, if I remember correctly).  So, remember to update your PO files
>>> too!
>>>
>>> Cheers,
>>>
>>> Demetris
>>> http://op111.net/76 ‹ See what is new in WordPress 3.0!
>>> _______________________________________________
>>> wp-polyglots mailing list
>>> wp-polyglots at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-polyglots
>>>
>>
>>
>> _______________________________________________
>> wp-polyglots mailing list
>> wp-polyglots at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-polyglots
>>
>>
>
> _______________________________________________
> wp-polyglots mailing list
> wp-polyglots at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-polyglots
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-polyglots/attachments/20100730/dc257512/attachment.htm>