-
Notifications
You must be signed in to change notification settings - Fork 141
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
What to do about reverted PRs and compatibility with 2.6.2 #703
Comments
It is not just agda/cubical itself but also agda/agda is checking I can think of at least two possible "solutions"
|
We could have an |
If Agda 2.6.3 has breaking changes which are not compatible with any commit on agda/cubical, then it won't work. In this particular case, though, agda/cubical defines cubical/Cubical/Reflection/Base.agda Lines 49 to 51 in 1c56f58
which is not used anywhere else. It is safe to remove this function so that the agda/agda on the master branch can still check agda/cubical without any issue.
However, IMO it is wise to have a branch like |
I meant an ad-hoc branch of agda/cubical, containing the commit that agda/master can reference. But I guess let's agree to call that branch We should probably write about this in |
Aha, I see. Thanks for the clarification.
That will be nice. I looked for guidance in vain and every release of |
I think it's been for the latest agda for a while, but currently there are not as many cubical changes going on so the incentives are reversed. |
I agree that making changes that keeps the library compatible with both Agda master and the latest release is the best (so @L-TChen can feel free to comment or remove the code that causes problems). If this is not possible I think that having an experimental branch would be good. As @xekoukou notes the documentation needs to be updated to reflect that the master branch of the library is now mainly intended to work on the latest release of Agda. I'm super busy these days, so can someone else make a PR with this change before we forget? |
#717 at least made changes to README and INSTALL, updating the phrase 'latest development version of Agda' with' to 'latest official release of Agda'. I guess there might still be other places that need some changing. |
Thanks! Closing this now |
@L-TChen I just reverted two of your PRs:
#701
#702
as they broke compatibility with 2.6.2 which is the current version we're using to develop the library. I hope this won't cause any new problems with the CI.
Before merging any PRs that break compatibility with 2.6.2 we should discuss if we want to do this. I don't think we should do this as it's such a headache to make sure that everyone is using the same version of Agda and it's much easier if we're all just using the latest official release. Once 2.6.3 is out we can update the library
The text was updated successfully, but these errors were encountered: