Hi, please read also the forwarded e-mail below from Jeffery. Jeffery´s proposal may be the fastest way to release, what we already know has to be done.
But we may be aware, that SOME bugs may always be hidden in ANY release and I would NORMALLY suggest to always complete a Turbine release with an Turbine Webapp release. As a result, if nobody complains (i.e. we get only unanimous consent, "do not care" remarks or no reply at all), I'll continue by sending a VOTE/RESULT around beginning of next week proposing to - drop the current Turbine webapp RC - targeting instead for the following RCs in this order: (1) Security Fulcrum v1.2 - still some more checks needed (2) Turbine v4.0.1 - (3) Turbine Webapp 1.2 - double checking (1) and (2) with tests in SNAPSHOT mode If someone else wants to help out, let me know it! Best regards, Georg Von: Jeffery Painter <[email protected]> An: Georg Kallidis <[email protected]> Datum: 08.12.2017 13:05 Betreff: Re: [VOTE] Release: Turbine-Webapp 1.0.2 archetype targeting Turbine4 on staged repository I think that is a good plan. I have no other issues with Turbine 4.0.1-SNAPSHOT release at this time (after fixing the input.encoding issue). And the patches you've made to fulcrum-security seem to work "well enough" for most use cases and we have identified what needs to be addressed going forward. Again, I don't use permissions (but after working on the Flux system, it looks like something I might use in the future), so I am happy we have been giving those a thorough test. I would go ahead and push those artifacts as soon as you feel is appropriate. On 12/08/2017 02:33 AM, Georg Kallidis wrote: > we may indeed decide to proceed to Turbine 4.0.1, but we have to keep in > mind then, that no Turbine Webapp would exist ready at hand to test > Turbine 4.0. Turbine 4.0 could be used in many, if not most parts. For the > security services you could use Fulcrum instead of Turbine (cft. to the > test examples), the one exception is permission revoke/grant, which must > be fixed in Fulcrum. Of course we may find other fixables. > > If cancelling this release, we may then update NOW (after deciding process > is finished) Turbine Webapp to be based on Turbine 4.0.1-SNAPSHOT and > Fulcrum Security 1.1.2-SNAPSHOT. As a result we have to release 4.0.1 and > 1.1.2 before the next Turbine Webapp 1.0.2. Then we may (or may not) > include the Turbine - Flex module!? > > Best regards, Georg > > > > > Von: Jeffery Painter <[email protected]> > An: [email protected] > Datum: 07.12.2017 17:59 > Betreff: Re: [VOTE] Release: Turbine-Webapp 1.0.2 archetype > targeting Turbine4 on staged repository > > > > [ ] +1 release it > [ ] +0 go ahead I don't care > [X] -1 no, do not release it because > > I think we should delay the release until we finish fixing the few > remaining bugs in fulcrum-security and also use the patched turbine > 4.0.1 core. Then we can point the new archetype at those instead, and I > can work on completing the turbine-flux module if you would like to > include it. > > > Thanks! > Jeff > > > On 12/05/2017 09:20 AM, Georg Kallidis wrote: >> Hi all, >> >> >> a release candidate for the >> >> Turbine Webapp Maven-Archetype, version 1.0.2 >> >> has been prepared! >> >> >> It contains the archetype for Turbine 4.0 Version. >> >> Tag: https://svn.apache.org/repos/asf >> /turbine/maven/archetypes/tags/turbine-webapp-4.0-1.0.2 >> >> Artifacts: >> https://repository.apache.org/content/repositories/orgapacheturbine-1026 >> >> >> Major changes are >> >> - Now based on Turbine 4.0! >> - Added some more examples (JSON, Localization, ..) >> - Schema changed using by default MySQL autoincrement instead of Torque > id >> broker. >> - JUnit Tests added to generated archetype project (mainly checking >> security managers) requiring MySQL, Torque Fulcrum Security and in parts >> Turbine. Part of the tests may only succeed in Turbine 4.0.1 version, > and >> are ignored. Tests must be activated manually with mvn test >> -DskipTests=false, more info in archetype folder docs/README.txt. >> - SLF4J support added >> >> >> Next steps: >> - Update to Turbine 4.0.1 >> - include Flex (Jar?) into Web App 1.0.3 >> >> >> >> Please verify this release candidate carefully and vote! >> >> [ ] +1 release it >> [ ] +0 go ahead I don't care >> [ ] -1 no, do not release it because >> >> >> >> Best Regards, Georg >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Jeff Painter CEO and Founder of JiveCast Software and analytics, made together http://jivecast.com 301 Fayetteville St. Unit 2301, Raleigh, NC 27601 (919) 533-9024
smime.p7s
Description: S/MIME Cryptographic Signature
