Skip to content

Test Roslyn-based GenAPI: regenerate source build reference packages #11225

@andriipatsula

Description

@andriipatsula

Due date: 9th of Dec. ETA ~4w. 1-2 days on a single package of various versions (usually up to 4-5 versions)

The main idea here is to regenerate all existed reference packages to prove that new GenAPI is capable to solve the problem. Gather statistics about issues still exists and where they could be solved (in GenAPI, Roslyn, etc.).

Currently in dotnet/source-build-reference-packages there are reference packages for 140 libraries, and each has [1-6] different version. Initial plan was to regenerate them all, but this no longer an option.

Below is the list of packages that A&D team suggested to start with (a representative set):

We need to generate a reference package with the Roslyn-based GenAPI, compare results with a baseline (a merged reference package) and gather statistics about issues/differences between the baseline and the generated codebase: what is the problem, is it the problem in the Roslyn, or the GenAPI and provide a number, % - occurrence of the problem.

We can make a 3-way comparison: Roslyn-based <-->Baseline <-> CCi-based GenAPI

Metadata

Metadata

Assignees

Labels

area-product-constructionIssues owned by the Product Construction team. Used to label epics and untriaged, loose issues.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions