Replies: 1 comment
-
|
I've just deleted as legacy branches as suggested. This has only a small chance of affecting anybody, as this should only affect legacy branches, but please report back if it does and we're happy to look into this. Currently supported development branches will continue to work as is. Plus, we can now focus on upcoming v3 branches as per https://github.com/orgs/reactphp/discussions/481 🎉 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We've recently renamed our
masterbranches to reflect the current major version like1.x/2.x/3.x/4.xas discussed in reactphp/promise#212 and related tickets.I've also checked all components and noticed we still have a number of legacy dev branches for deprecated versions laying around. These versions are no longer supported as per our LTS policy and haven't been updated in more than a few years. I'm not sure how much value these still provide, but I would argue that they can (and should) be deleted.
In particular, I would like to remove the following branches:
1.xstays.0.3and0.4should be removed.1.xstays.0.3and0.4should be removed.1.xstays.0.3,0.4and0.5should be removed.1.xstays.0.3and0.4should be removed.1.xstays.0.3and0.4should be removed.1.xstays.0.3should be removed0.6.xand0.7.xstay.0.3should be removed.2.x,3.xand4.xstay.1.x,2.xand3.xstay.1.xstays.1.xstays.1.xstays.1.xstays.See this gist for all details: https://gist.github.com/clue/3f0382e8d86d8998fda7744d2d0a7995
This way, all projects would be aligned nicely. This would also be a nice preparation for future
3.xand/or4.xbranches as discussed in https://github.com/orgs/reactphp/discussions/472.If there are no objections, I would like to go ahead with this in a week or two.
Beta Was this translation helpful? Give feedback.
All reactions