You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2021/02/20 12:44:14 UTC

[GitHub] [openwhisk] vrann commented on pull request #5065: Upgrade to Akka 2.6.11

vrann commented on pull request #5065:
URL: https://github.com/apache/openwhisk/pull/5065#issuecomment-782634471


   @bdoyle0182 Thanks for the feedback!
   I would definitely support more community discussion around the upgrade. I'm new to this community and with this PR wanted to put something which can help to bring the discussion forward. What do you see can be the next steps?
   
   From our side, we are working on the new feature built with akka typed, which we would like eventually contribute back to this project as well. So right now there are few choices, either a) to downgrade it to akka classic, or b) to upgrade openwhisk to akka 2.6 or c) to keep our own fork. I can tell that the option b) is my favorite and I would be glad to help to move it forward as far as I can.
   
   Regarding your comments:
   1. It would be very valuable to learn the problems with upgrade you faced. That should probably be part of the documentation which goes with this PR?
   2. I was planning to volunteer some time to an effort of FSM upgrade. If there is an interest in community for this work I can collaborate. I believe it is as valuable as just the akka upgrade.
   3. To the best of my knowledge, everything written with the classic akka would still work with the akka typed. Would it be logistically easier to keep these two activities separate and then upgrade scheduler on typed at some point? Are there any other changes in scheduler which relies on 2.5? Or is it just a matter in which order we merge these two changes?
   4. Regarding 2.6.11 noted. I will start upgrading to 2.6.12


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org