You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
deprecate 2.0.0-rc* and 2.0.0-alpha* as they are missleading now that 2.0.0 is different and we plan to incorporate all the changes in 3.0.0 (@UlisesGascon )
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 😅
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
So far seems like we need to organize a bit the branches, before we start with #1310 to prevent having more mess
GitHub
lts
branch tov2
(@UlisesGascon )master
tov2
: there are some docs changes relevant Sync changes to v2.x #1312 (@UlisesGascon )v2
the default branch (@UlisesGascon )master
branch (@UlisesGascon )v3
fromv2
and cherry-pick the relevant changes fromv2.0.0-rc*
andv2.0.0-alpha*
(v2.0.0...v2.0.0-rc.4) (@UlisesGascon )npm
2.0.0-rc*
and2.0.0-alpha*
as they are missleading now that 2.0.0 is different and we plan to incorporate all the changes in 3.0.0 (@UlisesGascon )WDYT? @expressjs/express-tc @bjohansebas
The text was updated successfully, but these errors were encountered: