microsoft / microsoft/brainsmith
Vivado 2025.1 migration
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 60
- Forks
- 12
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 2
Description
Verify all flows on Vivado 2025.1 and set it as the default versio
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Begin by locating the Vivado flow configuration and current version references, then run all existing flows with Vivado 2025.1; done means every flow passes and 2025.1 is the default version.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100