-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Orleans 2.X #2143
Comments
As each of these stages (Crawl, Walk, Run) will include it's own discussions and a number of sub-tasks, would it make sense to open a similar issue for each stage as we enter it? This is a good high level view, but if this ends up including all of the discussion and details of the full port it will get a bit unruly up in here :) |
@jason-bragg yep! That is the idea as we agreed on the meetup. I'm writing the Crawl main issue right now and will refer it here. Gimme a few minutes. |
BTW, anyone with write access please feel free to update/edit this or the related sub-issues with anything you feel necessary. |
Question - when you say port to .Net Core, do you mean only .Net Core will be supported, or the full .Net framework will still be supported? I think it's very important the full .Net framework is continued to be supported, as many other libraries do as of day. |
@Eldar1205 See #2145 for more information, but the short answer is yes it will support full framework as well as core. If you have any questions about core support, I'd ask it over there. |
Yes, when we say "Target |
Is there a timeline for 2.0? |
We are about to publish a beta in nuget.org very soon, and hopefully if everything goes well, we can push the final release a month after that (not an unmovable commitment, but we are targeting that). |
Yes, I am super exited to use in .NET Core :) |
We are going to evaluate orleans in upcoming .NET Core project. Thanks in advance. |
We just published 2.0.0-beta2 packages to NuGet.org. Is should be good for new projects. While there will still be some changes before final, they should not impact most applications. We hope 2.0.0 final is only a few weeks away. Although with the end of the year holidays many people will be on vacation. You can join the upcoming meetup this Wednesday that will be focused on Orleans 2.0 - https://github.com/OrleansContrib/meetups#meetup-15-orleans-20-with-the-core-team. |
Any update you can share ? |
We are hoping to publish 2.0.0-rc1 tomorrow. If all tests run fine. |
This issue will be a "root" issue to track the progress on 2.0 milestone following the steps agreed at Meetup 10.
The main target on this milestone is the port to .Net Core but other features like enhanced deployment & cluster management in multiple hosting environments, pervasive DI, new persistence layer, etc., but all them basically follow the major goal to be compatible with .Net Core.
The initial strategy is to keep working on the port on
master
branch by having a separated and temporary solution where we will target.Net Standard
while using new projects "linking" to the.cs
files and following the guidelines here (thanks to @jdom for this briliant idea). The reason for that strategy and not the current one (have a separated branch for that) is to reduce the merge complexity and be able to hotfix and add non-breaking changes to 1.3.x releases while we still working on .Net Core port. We will focus on have any breaking change on hold to 2.0 but that doesn't block us from having new features being released under 1.x.y tag.The tasks will be distributed across multiple phases defined as CRAWL, WALK and RUN. So, here is the list of macro-tasks that we should cover in this story and each one of them will be tracked by a separated issue and its sub-issues referenced here.
Note: #368 was tracking it before but since most of the issues there were already completed and we moved to a new strategy, from now on, lets keep the discussion about that here.
The text was updated successfully, but these errors were encountered: