Skip to content

Normalize the repo branches and versions #1313

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 7 tasks
UlisesGascon opened this issue May 20, 2025 · 2 comments
Open
1 of 7 tasks

Normalize the repo branches and versions #1313

UlisesGascon opened this issue May 20, 2025 · 2 comments
Assignees

Comments

@UlisesGascon
Copy link
Member

So far seems like we need to organize a bit the branches, before we start with #1310 to prevent having more mess

GitHub

npm

WDYT? @expressjs/express-tc @bjohansebas

@LinusU
Copy link
Member

LinusU commented May 20, 2025

Regarding:

create a new branch v3 from v2 and cherry-pick [...]

I think that it might be easier to rename explore-new-api to v3. I think that many changes that has since happened on master (or lts, v2, etc.) isn't relevant to explore-new-api, since I basically rewrote the package from scratch (42a9e3b).


Regarding the plan as whole, I'm not sure what's been discussed in the meetings since I haven't had time to be actively involved lately, sorry about that 😞

But it sounds good 👍

The only thing to keep in mind is that if I remember correctly, npm will consider 2.0.0 compatible with e.g. 2.0.0-rc.4. So this might be confusing/breaking for people that are currently using the release candidates for 2.0.0, that will now get a completely different package as 2.0.0 😅

@ctcpip
Copy link
Member

ctcpip commented May 20, 2025

I would prefer to keep modes of working (such as branching strategy) consistent, wherever possible. As such, it seems like we should keep master (probably rename it to main), then that becomes the tip/head dev branch (default), like we do with express.

v2 branch would remain v2. explore-new-api would become the main branch, if that is going to be the v3 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants