From: Carlos P. <cpa...@ce...> - 2016-03-18 09:07:52
|
Hi all, As you may know, we have been working for almost 3 years to implement the next major version of Taurus (version 4.x) in parallel with developing the 3.x version. A very important milestone has been reached now with the promotion of version 4.x to the official develop branch. Since the develop branch is the main base for new development, this means that any new features will from now on be added by default to the 4.x versions, while 3.x will be "frozen" and mostly just see essential hotfixes. The develop branch is also the base for the next official release, so hopefully the Jul16 release will already be of the 4.x series. The official documentation still needs to be adapted (help wanted!), but the following "Taurus Enhancement Proposals" document the main changes from the 3.x to the 4.x: http://sf.net/p/tauruslib/wiki/TEP3/ http://sf.net/p/tauruslib/wiki/TEP14/ We encourage you to try this new version and report any issues or contribute changes to help us in getting taurus 4 ready for release as soon as possible. Note: while the 4.x series is not 100% backwards-compatible with the 3.x series (hence the major version change), most 3.x based applications will work with 4.x out-of-the-box thanks to a compatibility layer that will log deprecation messages and hint ways to update the code to 4.x. For testing, just check out the develop branch from the official git repo, or, alternatively, install with pip using: ~~~~~~~~~~~~~~~~~~ pip install --egg \ git+http://git.code.sf.net/p/tauruslib/taurus.git@develop ~~~~~~~~~~~~~~~~~~ Cheers, Carlos (on behalf of the Taurus developers) -- +----------------------------------------------------+ Carlos Pascual Izarra Scientific Software Coordinator Computing Division ALBA Synchrotron [http://www.albasynchrotron.es] Carrer de la Llum 2-26 E-08290 Cerdanyola del Valles (Barcelona), Spain E-mail: cpa...@ce... Phone: +34 93 592 4428 +----------------------------------------------------+ |