Community Call Jan 21st, 2021

[SteveL-MSFT]

Agenda:

• 7.0.4, 7.1.1 releases
• SecretManagement AKV demo (Sydney)
• SecretManagement and SecretStore 1.0 GA
• Working Groups update (Joey)

Please add topics/questions below

[awakecoding]

Here's my list:

• PowerShell Azure CDN distribution (as opposed to GitHub Releases for pwshup initiative)
• PowerShell Native Host in Library (currently blocked on .NET team, but could solved in PowerShell).
• PowerShell Custom Transport Interface for 7.2 release (just want to make sure we have something before 7.2!)

[JustinGrote]

+1 on the Custom Transport Interface, it better be on the roadmap for 7.2 or I want my PR re-evaluated :)

[awakecoding]

@JustinGrote exactly, especially since what we've been suggesting is fair and simple, with very few code changes to review. From the last call I got the impression that custom transports were not high priority as opposed to other features, so I am very worried that a plugin architecture would get delayed and pushed out of 7.2. No matter what, I think we should plan for something that can reasonably make it into 7.2, or at least give the means for community members to give a helping hand on this one.

[awakecoding]

@SteveL-MSFT I just noticed that the date says January 20th, but that's tomorrow (Wednesday). Isn't the call supposed to be on the 21st, or Thursday?

[SteveL-MSFT]

@awakecoding Fixed!

[kborowinski]

Will profiler make into Preview 3?

[SteveL-MSFT]

That profiler PR is still a draft PR which means it's not ready for review, so unlikely to make it by preview 3.

[vexx32]

Any chance that PowerShell/PowerShell#9900 gets sufficient attention to get pulled in over the next month or two?

There are a couple outstanding things y'all probably want to think on, and I get it, I'm just conscious this PR has been delayed / pushed back several times now, so if it's still something that's desired, it needs more than the once-every-6-months attention it's been getting or we'll be picking away at it for the next decade. 😅

[iSazonov]

That profiler PR is still a draft PR which means it's not ready for review, so unlikely to make it by preview 3.

@SteveL-MSFT It is ready for review. It works. I don't know whether it works so good or we need to search another approach. So please review the design.

[ili101]

ScriptBlock-Action-Preference PowerShell/PowerShell#6010. I see @SteveL-MSFT added it to Future milestone 6 days ago but @KirkMunro PR #219 wasn't merged yet into PowerShell-RFC/1-Draft.
I like the idea, are you considering approving it as a Draft?

[ili101]

Status update? PowerShell/PowerShellEditorServices#1295 (comment)

[JustinGrote]

@iSazonov I think steve means it's a draft PR in the github sense

So maybe promote it to a full PR so it is "ready to review" from a design perspective.

[iSazonov]

@iSazonov I think steve means it's a draft PR in the github sense

There are so many open PRs out there that it won't help. :-)
MSFT team could take a few days to clean up most of them and merge (or decline).

[iSazonov]

Need adjust release process PowerShell/PowerShell#14618

[JustinGrote]

@SteveL-MSFT @joeyaiello Thanks again for another great community call! Even if we don't agree it's a breath of fresh air to even be able to have the discussion rather than being punted to UserVoice where ideas go to die :)