-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failureslegacy-area-analyzerUse area-devexp instead.Use area-devexp instead.type-code-healthInternal changes to our tools and workflows to make them cleaner, simpler, or more maintainableInternal changes to our tools and workflows to make them cleaner, simpler, or more maintainable
Milestone
Description
I believe that there are four steps in this process:
- 1. Copy the code from the old repository to the new repository.
- 2. Fix the build system to build from the new location rather than the old.
- 3. Move the issues from the old repository to the new repository.
- 4. Update dartlang docs to point to new
READMElocation. - 5.
Remove the old repository.Make the old repo read-only. (Follow-up: Make deprecatedanalyzer_clirepo "read-only". #25192.)
We should wait to start this until 1.13 has shipped. When a step is finished, please mark it and assign this issue to the person responsible for the next step (or me if you don't know who that is).
Metadata
Metadata
Assignees
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failureslegacy-area-analyzerUse area-devexp instead.Use area-devexp instead.type-code-healthInternal changes to our tools and workflows to make them cleaner, simpler, or more maintainableInternal changes to our tools and workflows to make them cleaner, simpler, or more maintainable