Hi Jeff,

that´s great! We have to talk through this really .. 

Following is, what IMO taking place in the next two, three weeks, based on 
what could be expected from current state:

Thomas is in the process of preparing Intake, after this I would remove 
the two SNAPSHOTS (one of them already now resolved) in turbine core and 
prepare the release. Building the site may take some more time, but this 
could postponed or prepared all along. And yes, then we are able to 
release the archetype lastly! Do you want to volunteer for the release 
process? No other issues ASAIK!

After this is done the race is opened for the Turbine (Java) 8 IMO! We 
might declare this just plain text - details following .. as reading our 
mailing list we agree on this matter. I have added some comments/hints in 
pom dependencies, what might be done (+ release of Torque 4.1, which 
requires Java 8). More disrupting changes, which would mean e.g. an entire 
new configuration building, are probably tasks requiring some more 
(combined) effort. I think Thomas already made some efforts to migrate to 
velocity 2. But you might have some more insightful thoughts you would 
like to share! We should not forget about changing/adding more structure 
ton the repo (writeable GIT, another branch?). 

Best regards, Georg




Von:    Jeffery Painter <[email protected]>
An:     Turbine Developers List <[email protected]>
Datum:  15.02.2018 17:39
Betreff:        turbine core 4.0.1 release schedule




Hello everyone,

I am pretty deep into building out a detailed tutorial on getting 
started with Turbine 4.0 in Eclipse using the Maven archetype (I am 
quite sure it is a book now instead of a simple tutorial).  I was 
wondering when we can expect final releases of Turbine core and the new 
turbine-webapp archetype?

Once Thomas releases intake 1.2.3, is there anything else preventing 
releasing turbine 4.0.1 and subsequently turbine-webapp-4.0 version 1.0.2?

Let me know if there is anything I can do to help :-)  I am working from 
snapshots at the moment, and it isn't reasonable for me to enlist others 
to test out my walk through until these are released. I would also love 
to share it with you guys for feedback if/when you have time.

Thanks,
Jeff



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


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to