Closed tforkmann closed 2 years ago
Eh, I think those build system changes are fine.
However, we need CI updates.
This is fixed now. https://github.com/dotnet/fsharp/issues/12359#issuecomment-965105262
Anything else missing?
Well it's fixed in master. But not released
The fix is released in the compiler that targets the VS 17.1 update, which is released, so we can re-run this and plumb it through
Oh, lame, it's still a fucking preview
My understanding was that Feb/Mar time?
My experience tells me it will be a month, yes. But which one? Some manager in devdiv has a month on a ticket in Azure DevOps, and believes with all their heart that it'll ship that month. This has no actual bearing on when it will ship.
I thought that the code was all ready to go and there was some release window for NET 6 coming up that it was already scheduled for. Most likely I got that wrong ;-)
My experience tells me it's far less organized and planned than you'd expect.
It’s just weird that you don’t find any roadmap.
Current release target for 6.0.2xx is early February, but we're still catching up from the holidays + a snafu or two with the 6.0.1xx service releases in December, so that could slip (as always).
@tforkmann roadmaps are just lies an organization agrees to tell its users 🙂
Linking https://github.com/giraffe-fsharp/Giraffe/issues/500 - not that it's required per say, but there's a dependency chain I want traced
Hi there,
dotnet 6.102.
Do you guys know if the fix made it into the newest release?
Cheers,
Tim
Dunno, about to find out :)
At least for macOS developers, the answer is no: https://github.com/dotnet/fsharp/issues/12359#issuecomment-1033948432
If anyone has a windows or linux machine and can confirm or deny the fix that'd be great
Ok could you please try again? 6.0.200 got released today. Thanks :)
@tforkmann I looked it over and everything looks kosher to me. README update would be needed too but that isn't critical. Anything else here you think is WIP?
@cartermp Just changed the README a bit. Could do more later. Do think there is more open issues. I added you and @baronfel as reviewer.
@baronfel Hope thats how you wanted it to be implemented. Never saw that before so hope thats correct now.
@tforkmann LGTM! Shipit!
Somehow it’s didn’t release directly … have to check why
Preview Version 0.16.0-preview03 just got release
Works for me...How about you guys?
can you please send the paket and fake changes in a separate PR?