Discuss state of r2 migration on Build WG meeting
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 542
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
Opening this issue just to track this in the meeting.
we are pretty much done with getting https://r2.nodejs.org/dist/ working.
we want to make sure we did not miss anything and discuss the next steps - mainly when we should pull the plug on the migration
the Cloudflare team asked for an estimated date so they can prepare (they are depending on https://nodejs.org/dist for installing node on their infra :), they want to avoid circular reference issue )
CC @flakey5 @ovflowd
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 reading the meeting discussion and reviewing the current state of https://r2.nodejs.org/dist/ alongside https://nodejs.org/dist. Identify any missed migration work and the conditions for safely shutting down the old path; the outcome is an agreed next step and estimated date for the migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- cloud, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100