Hi Georg, Looking back through your recommended release schedule. I have gone through and updated the JavaDocs for yaffi, testcontainer, factory and parser - they all generate proper reports/javadocs now in the output. I think once the parent and assembly are released, these should be ready to put to a vote as well.
I am going to be out of town traveling the next few days, but I will be back next Wednesday. Have a great weekend. Thanks! Jeffery On 10/22/18 8:57 AM, Georg Kallidis wrote: > Hi Jeffery, > > I agree entirely. I just scanned through some of the poms, so we have to > keep in mind the dependencies > > - Turbine parent and Turbine Parent assembly, > turbine/maven/turbine-parent/trunk. - should be release first. > - Align all Fulcrums, check again, and prepare an release candidate: > first: testcontainer, factory > then: pool, localization, parser, intake, yaafi-crypto, yaafi, > crypto, mimetype, quartz, security (still with Torque 4.0) (Turbine > depends on them all and all depend on testcontainer, some on factory). > - Turbine-Core, Turbien-Archetype > - Turbine-Site, Fulcrum-Site (!) > > Turbine parent may be released lazily. Parents could be announced end of > this week, and released next week, if no one complains. Then the first two > Fulcrums (testcontainer, factory) could be prepared the following week and > the bulk of Fulcrums may then come in November, finally Turbine may then > be made ready in December or January. In parallel with Turbine I like to > check Turbine-archetype .. > > What do you think? I or Thomas could prepare a Turbine parent RC hopefully > this or next week, afterwards you may be release as many Fulcrums as you > can ;-). > > Best regards, Georg > > > > Von: Jeffery Painter <[email protected]> > An: Turbine Developers List <[email protected]> > Datum: 19.10.2018 16:24 > Betreff: Planning releases? > > > > Hi guys, > > Any thoughts on planning some new releases? I have been > building/testing against Turbine 5.0 the last two weeks. One instance > has been up and running since Monday scraping data and so far I have no > complaints :-) > > I was going back through fulcrum-cache and I was able to backport most > of the code changes Thomas had made over the years to the last known > good build (tags/CACHE_1_1_0) and it is mostly working - some of the > tests still fail after generification, but pass without generics and > still calling the generified API... a little odd, but again I am no > expert on the caching stuff. > > I would be in favor of at least releasing all other fulcrum components > so we can get turbine pointing at those releases instead of snapshots. > > Let me know what I can do to help. > > Thanks! >
signature.asc
Description: OpenPGP digital signature
