Merged
Conversation
This file contains hidden or 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
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.
This PR brings zx-related adaptations into master. zx/zomp documentation.
This has some effect on the release process.
gprocis published in theuwigerrealm (realm file).My intention is to set git version tags that follow the version control in zx, so the release process will be:
In zx:
(after testing, checking in and pushing to github)
After this, we can tag the commit with
git tag -a 1.1.0 -m "1.1.0"and release to hex.Note that building with
rebar3works just like before. Thezompify.shscript cleans up arebar3build forzomppackaging.