[wp-trac] Re: [WordPress Trac] #8729: "WordPress 2.7 is available! Please update now." Displayed in WordPress 2.7 Dashboard.

[WordPress Trac]

#8729: "WordPress 2.7 is available! Please update now." Displayed in WordPress 2.7
Dashboard.
--------------------------+-------------------------------------------------
 Reporter:  miqrogroove   |       Owner:  nbachiyski
     Type:  defect (bug)  |      Status:  assigned  
 Priority:  high          |   Milestone:  2.8       
Component:  i18n          |     Version:  2.7       
 Severity:  major         |    Keywords:  has-patch 
--------------------------+-------------------------------------------------

Comment(by xibe):

 Replying to [comment:30 Denis-de-Bernardy]:
 > Quite honestly, I'd be curious to know how long it takes for the mo file
 to get updated.

 It depends entirely on each locale's team. Some team try to make sure the
 locale version is available in the hours following the release of WP,
 while other teams catch up in the following weeks, even months sometimes.

 > For this reason, we could consider that a week or two after the initial
 WP update is a long enough delay. If the mo isn't done by then, we could
 consider that nobody is maintaining the mo file.

 We can't work that way. A team should not be dropped just because they are
 slower than others. I'd rather have a team working at their pace on a
 translation, than no team at all. To each his own.

 > Along the same lines, it might make sense to only enforce the above-
 mentioned behavior for major updates (e.g. 2.6 to 2.7), and not for minor
 ones (2.6 to 2.6.1). After all, minor updates are frequently security
 related, and it's better to have wrong caption or two than a hopelessly
 hacked site.

 Agreed, although I fail to see how not upgrading a locale version can
 prevent hacking. Maybe I misunderstood you :)

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/8729#comment:32>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software