Release Agda 2.6.3 #6055
Comments
jespercockx
added
not-in-changelog
|
I'm in GMT-3 (America/Sao_Paulo), and Wednesday works for me 🙂 |
|
Let's have a meeting on Wednesday at 15:00 (GMT+2) / 10:00 (GMT-3) then. I'll send you the details in private. |
|
Next meeting: October 5th |
|
There is lots of closed issues without milestone which should potentially be added to 2.6.3, so that they appear in the changelog. I get started on this. |
I am done going through the relevant issues without a milestone and assigned these. Fingers crossed, we should now not have any issue closed by 2.6.3 which is not on the milestone. |
Now there is only #6220 left from this list. We could start a release candidate as soon as @nad 's PR #6221 has landed in |
|
This is the list of closed issues currently computed by
Issues that get removed from the changelog by adding suitable not-in-changelog tags are |
|
@andreasabel What needs to be done re.
this? |
|
@plt-amy : I meant that if an issue has a non-descriptive title, go there and edit it (don't edit it in the list above). |
|
Do you really want to advertise this hack (which is documented in the user manual)? The option is included as a (not very good) workaround for those who encounter error messages like "commitBuffer: invalid argument (invalid character)". If that error message is printed, then Agda will hopefully inform the user about possible workarounds, including the use of Lines 337 to 355 in 1a89181 |
Fine with me if you want to keep it under the radar. |
Yes. I'll prepare the RC. |
|
In the CHANGELOG for 2.6.2.2 (and other versions too) we included a section with highlights. Could someone add some highlights for 2.6.3? |
It seems we are ready for creating the release branch. Right? |
There are some PRs left with milestone 2.6.3 which I expect to land very soon. You could wait for these to save you some cherry-picking and keep a simpler commit history. There are also
|
|
I just moved issue #5577 to the 2.6.3 milestone. |
|
Updated list of currently closed issues in for the 2.6.3 changelog (doesn't include #5577 and other to-be-closed issues): Regressions in Agda 2.6.0
Regressions in Agda 2.6.1Internal errors triggered by rewriting:
Regressions in Agda 2.6.2
Other bug fixes and new features
|
|
Should issues that are mentioned explicitly in the changelog be included in the list that is added during the release process? |
|
Usually we apply the label |
Ok, didn't remember this trick. |
I thought that enhancements were not part of the list, because enhancements are typically documented in the changelog. Anyway, I've added
Isn't that list automatically generated? I don't see the point of that exercise. |
Thanks.
That list was originally automatically generated, but now is a manually maintained worklist. |
|
Issue #3714 is not mentioned in the changelog. |
|
Here: Lines 216 to 218 in 6b55111 |
|
Agda 2.6.3 has been released. Great job every one! |
Yes, more or less. The question is if the std-lib test should use this branch, or something like "v1.7.3". |
* Removed Cabal test-suite * Removed -Werror * Cleaning stack-XYZ.yaml files + Removed QuickCheck dependency + Removed tasty-* dependencies + Removed local package (src/size-solver)
This reverts commit 15f62c7.
* Removed Cabal test-suite * Removed -Werror * Cleaning stack-XYZ.yaml files + Removed QuickCheck dependency + Removed tasty-* dependencies + Removed local package (src/size-solver)
This reverts commit b00db9d.
This reverts commit b9941c5.
* Removed Cabal test-suite * Removed -Werror * Cleaning stack-XYZ.yaml files + Removed QuickCheck dependency + Removed tasty-* dependencies + Removed local package (src/size-solver) [ci skip]
This reverts commit b9be326. [ci skip]
This reverts commit 22d4978. [ci skip]
* Removed Cabal test-suite * Removed -Werror * Cleaning stack-XYZ.yaml files + Removed QuickCheck dependency + Removed tasty-* dependencies + Removed package section [ci skip]
…(RC2)." This reverts commit 86fd657.
… the Docs." This reverts commit b0a9a4d.
* Removed Cabal test-suite
* Removed -Werror
* Cleaning stack-XYZ.yaml files
+ Removed QuickCheck dependency
+ Removed tasty-* dependencies
+ Removed package section
[ci skip]
This reverts commit b499d12.
|
I just realized 2.6.3 was released with |
It would be good to work towards a release of 2.6.3 before the next Agda meeting, i.e. by the end of October.
To get us started, I went through all the issues with milestone 2.6.3 and moved many of them to either the icebox or the (newly created) "later" milestone, which is intended for issues that we are planning to fix in an upcoming release but not the next one. If you can, please take a look at the issues with that new milestone and comment or reassign the milestone if you disagree.
This currently leaves us with 39 issues that still have the 2.6.3 milestone, perhaps it would be good to restart the weekly online developer meetings to discuss who can work on which of these issues and which ones could be postponed. @UlfNorell @andreasabel @nad @plt-amy @Saizan since you are currently assigned to one or more of the issues with milestone 2.6.3, would you be available for a meeting in the coming week, perhaps Wednesday afternoon? (What time zone are you in @plt-amy ?)
The text was updated successfully, but these errors were encountered: