We don’t agreed on a release date for Xtext 2.13 yet, but for Photon Xtext 2.15 
is scheduled preliminary.

[1] 
https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg14690.html 
<https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg14690.html>


> Am 20.09.2017 um 10:03 schrieb Ed Willink <e...@willink.me.uk>:
> 
> Hi
> 
> Xext 2.13.0 seems to exhibit good compatibility; QVTd builds and tests with 
> 2.13.0 without noticing.
> 
> Xtext tends to do more than one minor release per year, so a 2.14.0 before 
> Photon might be expected. Much better to set the upper bound as next major 
> version; i.e. 3.0.0 and only set it lower once there is a known problem to 
> workaround.
> 
>     Regards
> 
>         Ed Willink
> 
> 
> On 20/09/2017 08:47, Lorenzo Bettini wrote:
>> On 19/09/2017 22:48, Jeff Johnston wrote:
>>> Thanks Abel.  Tomorrow is fine to get our patch in.  I sent a note to
>>> the EMF Parsley and Xtext contacts
>>> as the same error occurs for EMF Parsley.
>> Hi
>> 
>> >From what I understand EMF Parsley is now temporarily disabled in the
>> aggregation.  We'll port it to Xtext 2.13 soon and then re-enable it.
>> 
>> cheers
>>      Lorenzo
>> 
> 
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus <https://www.avast.com/antivirus>
> 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 
> <mailto:cross-project-issues-dev@eclipse.org>
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev 
> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to