|
From: Maria-Teresa,
Nunez-Pardo-de-Vera <mar...@de...> - 2015-05-08 09:31:55
|
Hi Carlos,
Desy also votes 'yes' for acceptance.
Many thanks for the work.
Regards,
Teresa
On 05/08/15 11:17, Carlos Pascual wrote:
> Hi all,
>
> The implementation of TEP3 [1] (which, among other things, makes
> taurus.core independent of Tango) has finally reached the point in which
> we can consider it complete.
>
> Therefore we ask the community to evaluate it **and for each institute
> to vote whether TEP3 should be passed to ACCEPTED**.
>
> Also, Tiago kindly offered to do the integration work in case it is
> accepted.
>
> In order to test, you just need to check out the tep3 branch from the
> official taurus git repo [2].
>
> Please note that if/when TEP3 is integrated into develop, the taurus
> major version number should be changed to 4.0.0 to reflect the fact that
> some TEP3 changes in the model name syntax are not 100% backwards-
> compatible[3].
>
> We hope you find TEP3 as interesting as we do.
>
> Cheers,
>
> Carlos (Falcon) & Carlos (Pascual)
>
> ps: Naturally, ALBA's vote is "yes" for acceptance.
>
>
> Notes:
> [1] http://sf.net/p/tauruslib/wiki/TEP3/
> [2] git://git.code.sf.net/p/tauruslib/taurus.git
> [3] Do not worry: pre-tep3 model naming is supported via a backwards-
> compatibility layer which handles all but a tiny fraction of pre-tep3
> names. The ones not supported are those which would be ambiguous, but
> they can be manually adapted very easily.
>
>
|