Replies: 1 comment
-
|
+1 Also - related to what @jborean93 says - It is increasingly hard to tell our customers to trust the future use of PowerShell when it looks like it is already being ignored. If this release is 5-6 behind, what will happen to 7.7? 8.0? It simply shouldn't be this much of a delay in a properly supported language - at least not without good communication and reason. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there anything the PowerShell team can communicate around the delay on PowerShell 7.6? It is approaching 2 months since the last preview and 3 months since .NET 10 was officially released. It seems like we still need an rc1 so by the time the official release we will have lost maybe 5-6 months of the total 3 years in the .NET lifecycle and 7.5 will be EOL in 2-3 months time.
It's been a bit frustrating trying to tie support for PowerShell 7 in our product when we can't even determine when the official releases happen.
Beta Was this translation helpful? Give feedback.
All reactions