Update README.md and remove references to Bazel #906
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
endgame
approved these changes
May 1, 2023
Yes - although if there's no clear objective for RC2 I'd also be happy to just go for a 2.0 release proper? |
|
I'd like to get one more round of botocore updates and checks for new regions etc in before we go to Hackage. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes the references to Bazel and adds instructions for using Amazonka as a source/git dependency.
There's still no analogue to Bazel's
//:docstarget to build the website documentation - and asstandalone-haddockis dead at this point it looks like waiting for cabal haddock-project to become generally available is more sane than the usual patching/templating/modifying Haddock's output to support a standalone bundle suitable and custom index/landing page for the website.See: