Skip to content
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

Narrow the feature gap between EF Core and EF6 #24106

Open
21 of 33 tasks
Tracked by #30173
roji opened this issue Feb 10, 2021 · 9 comments
Open
21 of 33 tasks
Tracked by #30173

Narrow the feature gap between EF Core and EF6 #24106

roji opened this issue Feb 10, 2021 · 9 comments
Labels
Milestone

Comments

@roji
Copy link
Member

roji commented Feb 10, 2021

This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.


There are still some scenarios supported on EF6 which aren't on EF Core. In order to make it as easy as possible to transition from EF6 to EF Core, we plan to close this gap as much as possible, although some scenarios will remain unsupported by design.

Done in 6.0

Done in 7.0

Done in 8.0

Backlog

@ankitmatrix08
Copy link

ankitmatrix08 commented Jun 23, 2022

@AndriySvyryd May I know why this has been removed from 7.0.0 milestone as before it was on scheduled and confirmed here ?

@roji
Copy link
Member Author

roji commented Jun 23, 2022

@ankitmatrix08 this has been changed to the "epics" milestone, which is where we track over-arching epics which track specific issues. It's just a "book-keeping" change - the concrete issues tracked here are still in the 7.0 milestone and are still planned (though that doesn't mean all will necessary make it in).

@ajcvickers
Copy link
Member

ajcvickers commented Jun 23, 2022

@dotnet/efteam We need to discuss Epics again. When do we close them? If someone votes for an Epic, what are they voting for?

@roji
Copy link
Member Author

roji commented Jun 23, 2022

I personally like to have epics in the milestone, allowing both ourselves and users to track work in the milestone for a high-level item. Here's how Npgsql does it - it's been very useful for me (and hopefully for users) to be able to drill down like this.

For work that's ongoing across multiple versions (e.g. EF6 parity), each milestone epic can simply reference the one before etc., and we can have one in the backlog for unplanned work.

But we should probably discuss in a design meeting...

@ankitmatrix08
Copy link

@ankitmatrix08 this has been changed to the "epics" milestone, which is where we track over-arching epics which track specific issues. It's just a "book-keeping" change - the concrete issues tracked here are still in the 7.0 milestone and are still planned (though that doesn't mean all will necessary make it in).

@roji That's the thing, since it's not clear as to what all items will make it to the 7.0.0 (among ef6-parity) release hence the confusion and trouble for us decide our migration.

@roji
Copy link
Member Author

roji commented Jun 23, 2022

@ankitmatrix08 the milestone on each individual issue determines whether it's in the plan or not. This issue is just a list referencing those issues for easier tracking; we generally update it to keep it in sync, but that may not happen right away. Just check individual issues directly.

@ajcvickers ajcvickers added the composite-issue A grouping of multiple related issues into one issue label Dec 6, 2022
@ajcvickers ajcvickers modified the milestones: Epics, Backlog Dec 6, 2022
@mairaw
Copy link

mairaw commented May 26, 2023

I'm cleaning up the .NET 6 project. This shows as completed on the project dashboard but still open here. Not sure if this needs any updates.

@roji
Copy link
Member Author

roji commented May 30, 2023

@mairaw thanks, we're using this to track overall EF6 parity issues across versions (6.0, 7.0, backlog...). Short of creating a separate issue for things we did in 6.0 and tracking that in the project, I think it makes sense to simply remove this.

@mairaw
Copy link

mairaw commented May 30, 2023

Sounds good @roji. Thanks for making the update.

@AndriySvyryd AndriySvyryd removed the User Story A single user-facing feature. Can be grouped under an epic. label Oct 18, 2023
@ajcvickers ajcvickers removed their assignment Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants