Description

Darwin (DarwinJS)

opened on Jun 5, 2019

Issue body actions

Summary of the new feature/enhancement

Maintain PowerShell 7 Compatibility Profiles (https://github.com/PowerShell/PSScriptAnalyzer/tree/development/PSCompatibilityCollector/profiles) throughout the preview release phase so that everyone can easily understand how the releases are making progress to supporting their existing PowerShell code.

It might actually also help generate knowledge about what needs addressing before a GA release.

While it is understood that these would eventually be made available - this issue is to lobby for these profiles to become a deliberate and managed part of each agile iteration of PowerShell 7.

Proposed technical implementation details (optional)

Brainstorm and scope what these profiles should cover.
Release a set of PowerShell 7 compatibility profiles with each preview release.

/cc Joey Aiello (@joeyaiello) Steve Lee (@SteveL-MSFT)

Reacted by Ilya

Activity

1. Darwin (DarwinJS)

   added

   Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bug

   on Jun 5, 2019
2. SteveL-MSFT commented on Jun 6, 2019

   

   Steve Lee (SteveL-MSFT)

   on Jun 6, 2019

   Member

   More actions

   Interesting idea. cc Rob Holt (@rjmholt)
3. rjmholt commented on Jun 6, 2019

   

   Rob Holt (rjmholt)

   on Jun 6, 2019

   Collaborator

   More actions

   Yeah good idea!

   For now they should go here (the profiles folder ships with PSSA and I already doubled the size of the module).

   We should implement PowerShell/PSScriptAnalyzer#1148 to really deliver this.
4. DarwinJS commented on Jun 6, 2019

   

   Darwin (DarwinJS)

   on Jun 6, 2019

   ContributorAuthor

   More actions

   Glad there is some energy around it!

   You guys might already be thinking this, but if the ScriptAnalyzer itself is a different dev team, I would say the PowerShell team should own the initiative on developing the PowerShell 7 data files - even if in the other repo - so that the objective of keeping high customer value by having it keep pace with the functional improvements in each sprint is realized.
5. Ilya (iSazonov)

   added

   Resolution-ExternalThe issue is caused by external component(s).The issue is caused by external component(s).

   on Jun 13, 2019
7. ghost closed this as completedon Jun 14, 2019
8. DarwinJS commented on Jun 14, 2019

   

   Darwin (DarwinJS)

   on Jun 14, 2019

   ContributorAuthor

   More actions

   msftbot seems to be miserly on closing issues eh?

   Reacted by Rain Sallow (/u/ta11ow)

Issue actions