Hi all,

happy New Year! 

I think, it's time to prepare a Turbine Core release 5.2. 

There is some experimental stuff in it, notabely DateTimeFormatterService, 
but a couple of tests exist and it seems to be ready to a certain degree. 
Nevertheless Turbine Core does currently depend on five Fulcrum components 
in state SNAPSHOT (testcontainer, intake, parser, security, yaafi) + 
parent pom in SNAPSHOT. 
We would have to first release the parent component v12-SNAPSHOT, if we 
want to update the minimal setting to Java 11 or revert the settings to 
the published version 11 in the new releases.

Overview of Fulcrum dependencies in Turbine 5.2-SNAPSHOT:

| name | version | last release | changes (commit for git diff) | remarks 
|
| testcontainer | 1.0.10-SNAPSHOT | end of 2020 | 
7d2f264371ec9d62d885212f1ef18c8b228bf650 | mostly cleanup and dependency 
updates
| intake | 2.0.1-SNAPSHOT | beginning of 2019 | 
44f7d9492d98c4e95d06a3da3380f7bf892bc26c | more complete test 
configuration 
| parser | 2.0.2-SNAPSHOT | end of 2019 | 
4df41f39b79827927256343f2652b078f6bb04f4 | mostly cleanup and dependency 
updates
| security | 2.1.1-SNAPSHOT | end of 2021 | 
cacbef75a874c4ab489ed76489a1235b885b5f97 | some Java 8/11 optimizations 
TODO Should we remove hibernate, as we are not able to follow security 
updates and update hibernate to a current version? | 
| yaafi | 1.0.9-SNAPSHOT | end of 2018 | 
a931f52fbfca71c0a4a0f72ce8bc82e1ead80065 | mostly cleanup of tests and 
dependency updates

What's your opinion? Do you agree? Did I miss something ? 

Should we wait and integrate / work on some important stuff? Should we 
just skip some Fulcrum updates? That is e.g. revert some dependencies in 
Turbine Core v5.2-SNAPSHOT (e.g. if we do not want the Java 11 baseline 
now in the new releases, we do not need parent 12)?

Should we proceed and start with the release bundles as set out (that is 
as release first parent, then Fulcrum components and last Turbine-Core) ?

Thanks!

Best regards, 

Georg

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

Reply via email to