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

July 2021 rough issue worklist #11801

Closed
3 of 5 tasks
KevinRansom opened this issue Jul 8, 2021 · 11 comments
Closed
3 of 5 tasks

July 2021 rough issue worklist #11801

KevinRansom opened this issue Jul 8, 2021 · 11 comments

Comments

@KevinRansom
Copy link
Member

KevinRansom commented Jul 8, 2021

And we're back with another month-ish of work. Here it is:

Note: 16.11 is a servicing-only release for us. We will not include any fixes unless they are high priority/regressions. All other feature work and bugs will be targeted for .NET 6/dev17.

@KevinRansom KevinRansom pinned this issue Jul 8, 2021
@KevinRansom KevinRansom changed the title July rough issue worklist July 2021 rough issue worklist Jul 8, 2021
@charlesroddie
Copy link
Contributor

No reference assemblies @TIHan ?

@baronfel
Copy link
Member

baronfel commented Jul 9, 2021

I'd expect that to be targeted for .NET 6 based on the fact that it's a new feature, not a high priority bugfix or regression.

@KevinRansom
Copy link
Member Author

@charlesroddie not at this time.

@nojaf
Copy link
Contributor

nojaf commented Jul 13, 2021

Any chance any of this will produce a new stable FCS package?
40 did not quite hit the mark for me. (Regression, that one last range bug I forgot).

@charlesroddie
Copy link
Contributor

charlesroddie commented Jul 14, 2021

@charlesroddie not at this time.

That's a shame because it was in the last two months' worklists and the feature would be the most impactful development for us in F# for the last few years, since it would reduce our average compilation times by a factor of 2-3.

@KevinRansom
Copy link
Member Author

@nojaf - I think we can release a 40.0.1 what bugs do you need fixed and in the release?

@KevinRansom
Copy link
Member Author

@charlesroddie priorities change all of the time. The feature may well come back, before long.

@nojaf
Copy link
Contributor

nojaf commented Jul 14, 2021

@KevinRansom if possible I'd like #11732 and #11734 to be in there.
One small caveat: this involves three PRs: #11736, #11733 and #11795.
#11781 would also be nice to have but is less blocking.

@vzarytovskii
Copy link
Member

Yeah, we had a bunch of fixes in since the last release, I guess it makes sense to release a new one. WDYT @KevinRansom?

@nojaf
Copy link
Contributor

nojaf commented Jul 23, 2021

Any update on a potential new FCS release @vzarytovskii @KevinRansom?

@TIHan TIHan unpinned this issue Aug 4, 2021
@dsyme
Copy link
Contributor

dsyme commented Aug 10, 2021

Closing out since August plan is up

@dsyme dsyme closed this as completed Aug 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants