[WG: I18N & L10N] i18n request for merges
neal.caidin at apereo.org
Mon Jul 15 07:59:59 PDT 2013
Right, I neglected to mention that important points that these are all
fixed issues and verified. Is your request to get them all into CLE 2.9.3
or just get them into 2.9.x (which might be post-2.9.3)?
On Mon, Jul 15, 2013 at 10:53 AM, Jean-Francois Leveque <
jean-francois.leveque at upmc.fr> wrote:
> Maybe I wasn't precise enough when discussing with Neal.
> I was the one doing the request based on the following JIRA query:
> (component = Internationalization OR component = Translation) AND ("2.9.x
> Status" = Merge or project = "CLE: Sitestats" AND "2.3.x Status" = Merge or
> project = "CLE: Profile2" and "1.5.x Status" = Merge) and status = Verified
> On 15/07/2013 16:19, Neal Caidin wrote:
>> Hi CLE Release team,
>> The Internationalization group is requesting a few more merges for CLE
>> 2.9.3 (we already have about a dozen we are targeting to get in) . It
>> seems to me, as has been suggested, that we may need to cut off any
>> additional request for merges for 2.9.3 soon.
>> Of these, to me, SAK-23734 looks like the most important because it is a
>> regression introduced in CLE 2.9.2 and is an Internationalization issue.
>> The others are translations which I assume are easy "low hanging fruit"
>> and little or no risk to add (except for adding extra work to our merge
>> What do you think? Should we add some or all of these in?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the i18n