Re: Re: Torque 4.1 dependencies changes required to test docker testcontainer in Turbine Core/Fulcrum Security Torque

Hi Jeff,

IMO Torque is almost release ready, at least concerning the code changes. 
Some cleanup, updating of and adding missing changes.xml (torque-site has 
old-changes with latest from Torque 3.3), and then it should be done. 
Though the latest code changes might require some small updates.

Of course, it's the Torque/Data PMC, which has to check and decide, but 
Thomas is in there? 

Best regards, Georg




Von:    Jeffery Painter <[email protected]>
An:     [email protected]
Datum:  09.10.2019 18:22
Betreff:        Re: Torque 4.1 dependencies changes required to test 
docker testcontainer in Turbine Core/Fulcrum Security Torque




What do we need to do to get a Torque 4.1 release out? I would start 
there, and if possible let's make it happen :-)

-

Jeff


On 10/9/19 11:02 AM, Georg Kallidis wrote:
> Hi all Turbine devs,
>
> for my latest tests and changes using Docker Testcontainers, which are 
not
> yet committed, I rely for the last steps on an update to Torque 4.1
> (configuration2). I would therefore like to update the dependencies in
> Turbine SNAPSHOT to Torque 4.1-SNAPSHOT.
>
> Caveat is, that we deepen our dependency debt in that we could then not
> release Turbine Core before Torque 4.1 is released (this is not true
> really: we could revert to Torque 4.0 again and disable all the 
dependent
> tests - at the moment only one of the new tests, which I have in mind,
> would require 4.1, but this might become the most interesting one, 
though
> I could commit some base tests already now). BTW, a Torque 4.1 release
> seems IMO quite overdue.
>
> I could restrict, what I want to do (using docker testcontainer) to
> Fulcrum Security Torque component, but the same question would arise
> there, as Turbine SNAPSHOT is dependent on Fulcrum Security Torque
> SNAPSHOT.
>
> What's your opinion?  Do you agree, that I could change Turbine POM or
> should I wait?
>
> Best regards, Georg
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]