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

Open
galvesribeiro opened this Issue Sep 12, 2016 · 13 comments

Comments

Projects
None yet
9 participants
@galvesribeiro
Member

galvesribeiro commented Sep 12, 2016

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.

  • CRAWL
    • .Net Core Compatible Binaries - #2145
    • Orleans 2.0 (beta is out)
  • WALK
    • Building on .Net Core
    • Testing on .Net Core
    • Orleans 2.X
  • RUN
    • Cross-platform testing
    • Orleans 2.Y

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.

@jason-bragg

This comment has been minimized.

Show comment
Hide comment
@jason-bragg

jason-bragg Sep 12, 2016

Contributor

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 :)

Contributor

jason-bragg commented Sep 12, 2016

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 :)

@galvesribeiro

This comment has been minimized.

Show comment
Hide comment
@galvesribeiro

galvesribeiro Sep 12, 2016

Member

@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.

Member

galvesribeiro commented Sep 12, 2016

@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.

@galvesribeiro

This comment has been minimized.

Show comment
Hide comment
@galvesribeiro

galvesribeiro Sep 12, 2016

Member

BTW, anyone with write access please feel free to update/edit this or the related sub-issues with anything you feel necessary.

Member

galvesribeiro commented Sep 12, 2016

BTW, anyone with write access please feel free to update/edit this or the related sub-issues with anything you feel necessary.

@jdom jdom added this to the CoreCLR milestone Sep 12, 2016

@sergeybykov sergeybykov modified the milestones: 2.0.0, CoreCLR Sep 12, 2016

@Eldar1205

This comment has been minimized.

Show comment
Hide comment
@Eldar1205

Eldar1205 Sep 13, 2016

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 commented Sep 13, 2016

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.

@TrexinanF14

This comment has been minimized.

Show comment
Hide comment
@TrexinanF14

TrexinanF14 Sep 13, 2016

Contributor

@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.

Contributor

TrexinanF14 commented Sep 13, 2016

@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.

@galvesribeiro

This comment has been minimized.

Show comment
Hide comment
@galvesribeiro

galvesribeiro Sep 14, 2016

Member

Yes, when we say "Target netstandard15" we mean cover both .Net Core as the full framework (more here). Remember that the major internal customer like Halo uses the full framework.

Member

galvesribeiro commented Sep 14, 2016

Yes, when we say "Target netstandard15" we mean cover both .Net Core as the full framework (more here). Remember that the major internal customer like Halo uses the full framework.

@SebastianStehle

This comment has been minimized.

Show comment
Hide comment
@SebastianStehle

SebastianStehle Oct 10, 2017

Contributor

Is there a timeline for 2.0?

Contributor

SebastianStehle commented Oct 10, 2017

Is there a timeline for 2.0?

@jdom

This comment has been minimized.

Show comment
Hide comment
@jdom

jdom Oct 10, 2017

Member

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).
In the meantime I'm sure you are aware of preview releases to myget.
Hope it aligns with your needs

Member

jdom commented Oct 10, 2017

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).
In the meantime I'm sure you are aware of preview releases to myget.
Hope it aligns with your needs

@SebastianStehle

This comment has been minimized.

Show comment
Hide comment
@SebastianStehle

SebastianStehle Oct 10, 2017

Contributor

Yes, I am super exited to use in .NET Core :)

Contributor

SebastianStehle commented Oct 10, 2017

Yes, I am super exited to use in .NET Core :)

@mo-esmp

This comment has been minimized.

Show comment
Hide comment
@mo-esmp

mo-esmp Dec 11, 2017

We are going to evaluate orleans in upcoming .NET Core project.
I'm wondering if v2.0 beta 1 is good enough for using in a project or not ?
How close are you to v2.0 release ?
Looking for recommendation on this case.

Thanks in advance.

mo-esmp commented Dec 11, 2017

We are going to evaluate orleans in upcoming .NET Core project.
I'm wondering if v2.0 beta 1 is good enough for using in a project or not ?
How close are you to v2.0 release ?
Looking for recommendation on this case.

Thanks in advance.

@sergeybykov

This comment has been minimized.

Show comment
Hide comment
@sergeybykov

sergeybykov Dec 11, 2017

Member

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.

Member

sergeybykov commented Dec 11, 2017

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.

@sergeybykov sergeybykov modified the milestones: 2.0.0, Backlog Jan 24, 2018

@talarari

This comment has been minimized.

Show comment
Hide comment
@talarari

talarari Feb 15, 2018

Any update you can share ?
Looking forward to upgrading to 2.0.

talarari commented Feb 15, 2018

Any update you can share ?
Looking forward to upgrading to 2.0.

@sergeybykov

This comment has been minimized.

Show comment
Hide comment
@sergeybykov

sergeybykov Feb 22, 2018

Member

We are hoping to publish 2.0.0-rc1 tomorrow. If all tests run fine.

Member

sergeybykov commented Feb 22, 2018

We are hoping to publish 2.0.0-rc1 tomorrow. If all tests run fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment