GitHub migration
Open
Nobody has claimed this yet.
meta
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
All tasks related to migrating our work from Microsoft-internal systems to GitHub.
Build System
- #161
- #162
- Port DLL export validation from MSBuild to CMake. (Or switch to
.def.) - Change the MSVC-internal MSBuild build system to invoke the STL's CMake build system.
- Delete
stl/msbuildand celebrate!
Tests
- Finish migrating
src/qa/VC/Libs/vcr/tests/cpp/Dev09_171913_tr1_windows_h_macros- And resolve Microsoft-internal VSO-936680
- #797
- #798
Documentation
- Write Contribution Guidelines.
- Drop the Roadmap.
Issues
- Finish migrating bugs.
- As of 2024-05-28: 107 bugs remain.
- Create bugs for vNext overhauls, collecting DevCom/VSO bugs (tagged vclibs-wcfb02) that were closed in the pre-GitHub Team Foundation Version Control vNext era.
- Finish migrating
todo.docxtoenhancementissues.- As of 2024-05-28: 5 pages remain.
- Migrate
lwg_issues_to_file.docxtoLWG issue neededissues.- As of 2024-05-28: 2.5 pages remain.
- Migrate
stl_requested_bugs.docxsomewhere (possibly the STL Wiki). - #2271
Done
- Migrated
status.xlsxto microsoft.github.io/STL/, powered by Chart.js. - #386
- #639
- #939
- Switched the internal build to use boost-math standalone:
- #2151
- #3077 (also migrated a Special Math test)
- Migrated tests from
vcr/tests/cpptostd:- #2507
- Unified libcxx's
expected_results.txtandskipped_tests.txt:- #3484
- #2310
- #820
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
Start by reviewing the unchecked sections and linked issues #161, #162, #797, #798, and #2271, then inspect stl/msbuild and the listed src/qa/VC/Libs/vcr/tests path. Done means the remaining build, test, documentation, and issue-migration checklist items are completed or tracked in focused issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, github
- Domain
- build-system, devtools, documentation, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100