Release current master? #318
Labels
No Label
blocked: dependency
blocked: info-needed
bug
duplicate
enhancement
fixed in HEAD
help wanted
hs:arrows
hs:brackets
hs:classes
hs:comments
hs:do-notation
hs:guards
hs:lists
hs:operators
hs:patterns
hs:records
hs:types
invalid
language extension support
layouting
needs confirmation
priority: high
priority: low
question
revisit before next release
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: hexagoxel/brittany#318
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Hi :)
I noticed there are features and bugfixes on
master
that aren't released.https://github.com/lspitzner/brittany/compare/0.12.1.1.x2...master
data
module .. where
If https://github.com/lspitzner/brittany/issues/47 isn't partially implemented and could lead to issues, one could consider releasing the current state as is. I ran it on a code base and the changes it produces seem to improve things (mainly because
data
is formatted).I technically have permission to do this, but I haven't done it before and I don't know the exact process.
📟 @lspitzner @eborden
Seconded. Can we please get a release with #312 merged?
It would be really awesome. As a workaround I ended up building own versions from master.
I‘d like to emphasize the need for this. Recent releases of haskell-language-server are not compatible with the last released brittany version. (at least I think so, because they switched to using @bubba's branch). And there are plans to release hls to hackage soon.
Making a small minor release of brittany would be great to help with packaging hls downstream. (i.e. right now we maintain two different brittanies in nixpkgs.)
EDIT: Oh, I am sorry for the noise. I realized, that they use a branch with not upstreamed changes for 8.10 compatibility.
@tfausak I think you should just bite the bullet and go ahead, what's the worst that can happen, a version has to be marked deprecated on Hackage?
Indeed, perfectionism leads to inaction. Please release the master + #312 🙏
I have built and released the current master branch as version 0.12.2.0.
I didn't merge #312 because the build failed with GHC < 8.8 and the tests failed with GHC 8.10. If you'd like to help, please see #324.
I didn't update the demo site (https://hexagoxel.de/brittany/) because I don't know how.
Thanks!
On Mon, Nov 16, 2020, 1:56 AM Taylor Fausak notifications@github.com
wrote: