The CHANGELOG is already 900+ lines long
I was planning to hold fire on the release until Agda 2.6.0 comes out, and then release shortly afterwards as v1.0?
Speaking of which I need to get a move on with any remaining non-backwards compatible changes...
This seems to be such a huge change that indeed waiting for 2.6.0 seems to 'make sense'. One big jump is better than two back to back.
Okay with the release candidate out for 2.6.0 we'd better get our socks on. I'll be doing a sweep of the issues.
Release happening on Monday (https://github.com/agda/agda/issues/3391)
Note that the release is ready and I'm only waiting to check that there are no more unforeseen changes in Agda 2.6.0 itself (e.g. 4a53aea5c67e69e894c011f2c27b387d2e08c44f). This means that the master branch no longer works with Agda 2.5.4.2.
When is the release happening?
When is the release happening?
The short answer is whenever Agda 2.6.0 releases. Presumably later this week. I'm waiting in case there are any more breaking changes before it does so (the library needed changes between release candidate 1 and release candidate 2).
There are also two last minute bug fixes in the pipeline here.
Version 1.0 of library has been released. Thank you everyone for all your hard work, couldn't have been done without everyone's help!
Thanks a lot Matthew!
Most helpful comment
Note that the release is ready and I'm only waiting to check that there are no more unforeseen changes in Agda 2.6.0 itself (e.g. 4a53aea5c67e69e894c011f2c27b387d2e08c44f). This means that the master branch no longer works with Agda 2.5.4.2.