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

Developers using filesystem APIs find them to work well with symbolic links #51605

Closed
4 tasks done
Tracked by #44314
carlossanlop opened this issue Apr 21, 2021 · 5 comments
Closed
4 tasks done
Tracked by #44314
Assignees
Labels
area-System.IO Bottom Up Work Not part of a theme, epic, or user story Cost:L Work that requires one engineer up to 4 weeks Priority:2 Work that is important, but not critical for the release Team:Libraries
Milestone

Comments

@carlossanlop
Copy link
Member

carlossanlop commented Apr 21, 2021

Proposed priorities for the issues we currently have open in the symlinks project.

P0

For items moved to .NET 7 please refer to #57205

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Apr 21, 2021
@ghost
Copy link

ghost commented Apr 21, 2021

Tagging subscribers to this area: @carlossanlop
See info in area-owners.md if you want to be subscribed.

Issue Details

Proposed priorities for the issues we currently have open in the symlinks project.

P0

P1

P2

Author: carlossanlop
Assignees: jeffhandley, carlossanlop, adamsitnik, Jozkee
Labels:

area-System.IO

Milestone: -

@iSazonov
Copy link
Contributor

@carlossanlop In PowerShell an symlink functionality was already added but we catch a lot of bugs, some (not all) ones was fixed. So your team could look and use the experience to make the work better in .Net.

@carlossanlop carlossanlop removed the untriaged New issue has not been triaged by the area owner label Apr 21, 2021
@jeffhandley jeffhandley added the Priority:2 Work that is important, but not critical for the release label Apr 23, 2021
@carlossanlop carlossanlop added Bottom Up Work Not part of a theme, epic, or user story Cost:L Work that requires one engineer up to 4 weeks labels Apr 23, 2021
@jeffhandley jeffhandley added this to the 6.0.0 milestone Jul 13, 2021
@adamsitnik
Copy link
Member

@jozkee @carlossanlop @jeffhandley should we move the things that are not done yet to a new issue and close this one? Or just move this to 7.0.0 milestone?

@jeffhandley
Copy link
Member

I'd prefer to update this one to reflect what was completed in 6.0.0 and file a new issue for 7.0.0 (that links to this one).

@adamsitnik
Copy link
Member

@jeffhandley done: #57205

@ghost ghost locked as resolved and limited conversation to collaborators Sep 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.IO Bottom Up Work Not part of a theme, epic, or user story Cost:L Work that requires one engineer up to 4 weeks Priority:2 Work that is important, but not critical for the release Team:Libraries
Projects
None yet
Development

No branches or pull requests

5 participants