Thank you for the information!
Regards, Julián
2014-05-29 15:02 GMT+02:00 Aleksandra Nenadic <[email protected]>:
> Hi Julián,
>
> Just to expand a bit on what Stian already said.
>
> The Taverna 3 release this summer will concentrate around the Command Line
> Tool and Server, where as the T3 Workbench will remain in the beta state
> for now. The reason for this is that releasing and testing the Workbench
> takes much much longer and has been holding us up in the past whereas there
> are no reasons not to release the Command Line Tool and the Server based on
> it.
>
> You will still be able use T3 Workbench (beta) with a few features missing
> or T2.5.x Workbench and export workflows in the new SCUFL2 format used by
> T3.
>
> Regards,
> Aleks
>
>
>
> On 29/05/2014 11:52, Stian Soiland-Reyes wrote:
>
>
> On 29 May 2014 09:03, Julián Garrido <[email protected]> wrote:
>
>> Hi Stian,
>>
>> Let me apologise if I should ask this to the mailing list.
>>
>
> I think these are exactly the kind of things that should be asked on the
> taverna-hackers mailing list. :) (CCed)
>
>
>
>> Could you give me some information about the timing of Taverna 3? We
>> would like to know it because we also have to migrate the [AstroTaverna]
>> plugin to the new architecture.I want to have an idea of when we should
>> start.
>>
>>
> We are planning on releasing Taverna 3 this summer - but we want to do it
> as a community effort and get involvement from the "Taverna hackers".
> Really you can start any time using the alpha 2 from Christmas:
> http://www.taverna.org.uk/developers/work-in-progress/taverna-3/
>
>
> What really remains is stabilizing version numbers and releasing the
> modules to the Maven repository - which now after the Github move we are in
> a much better position to be dealing with.
>
> Now we are merging changes to Taverna 2.5 "maintenance" branches into
> the "master" branch so that Taverna 3 will include bugfixes and features
> added since Taverna 2.3.
>
>
>
>
>> By the way, is the release of Taverna 3 directly related to moving
>> Taverna to Apache Incubator?
>>
>>
> I think it is realistically only Taverna 3 that could be moved to Apache,
> due to historical copyrights and licensing (Taverna 2 still pulls in bits
> and bobs from Taverna 1 which have a more complicated copyright history).
> However, we do not want to wait with Taverna 3 for the outcome of the
> Apache approach though!
>
> Here at myGrid we have thought that we want to let Taverna 3 'out' even if
> all the Taverna 2 functionality is not there, e.g. myExperiment perspective
> - and then drive it forward as a community effort so that the right things
> get worked on - let's say nobody actually use the "Save to Excel" button,
> well then we don't need to update that code for Taverna 3 API. It should
> also be easier to get involvement with a concrete and working product, even
> if it is not "feature complete" with the same tickboxes as Taverna 2.
>
>
>
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
taverna-hackers mailing list
[email protected]
Web site: http://www.taverna.org.uk
Mailing lists: http://www.taverna.org.uk/about/contact-us/
Developers Guide: http://www.taverna.org.uk/developers/
