-
Notifications
You must be signed in to change notification settings - Fork 372
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
Don't remove git cache objects that may be used #3831
Conversation
This is a quickfix, we can probably do better than that ; see ocaml#3828
This patch will be unnecessary when PR ocaml/opam#3831 is released.
This patch will be unnecessary when PR ocaml/opam#3831 is released.
This patch will be unnecessary when PR ocaml/opam#3831 is released.
This patch will be unnecessary when PR ocaml/opam#3831 is released.
Hi @rjbou @AltGr, I've seen you put the milestone 2.1.0 for this PR #3831 (which will be important to be able to run Do you confirm that the upcoming release of opam will be 2.1.0, or do you plan to make a point release 2.0.x beforehand? (in which case would this PR be eligible to be shipped along?) |
@rjbou @AltGr actually I've just seen that you opened some milestone for 2.0.6 :-) Hence my question: would it be feasible for you to integrate the fix from PR #3831 in opam 2.0.6 ? Kind regards, Erik |
There will be 2.0.6 & 2.1.0~beta releases. What we plan is that the 2.0 branch is the LTS one until 2.2.0, and its releases contains only bug fixes. By default, all PR are tagged 2.1.0 until backported to 2.0 branch for a release (cf. backported commits PRs). |
OK great! Thanks @rjbou for your explanation 👍 |
This patch will be unnecessary when PR ocaml/opam#3831 is released.
This is a quickfix, we can probably do better than that ; see #3828