releases.md - golang-github-vbatts-go-mtree (5bd602f6-34b2-411b-80f3-7d65781fd7d4/main)

Tree @5bd602f6-34b2-411b-80f3-7d65781fd7d4/main (Download .tar.gz)

.vscode
cmd
debian
pkg
test
testdata
xattr
.gitignore
.travis.yml
check.go
check_test.go
cksum.go
cksum_test.go
compare.go
compare_test.go
creator.go
entry.go
fseval.go
fseval_test.go
go.mod
go.sum
hierarchy.go
hierarchy_test.go
keywordfunc.go
keywordfuncs_bsd.go
keywordfuncs_linux.go
keywordfuncs_unsupported.go
keywords.go
keywords_linux_test.go
keywords_test.go
lchtimes_unix.go
lchtimes_unsupported.go
LICENSE
lookup_new.go
lookup_old.go
Makefile
mtree_test.go
parse.go
README.md
releases.md
stat_unix.go
stat_windows.go
tar.go
tar_test.go
update.go
update_linux_test.go
update_test.go
updatefuncs.go
updatefuncs_linux.go
updatefuncs_unsupported.go
version.go
walk.go
walk_test.go

releases.md @5bd602f6-34b2-411b-80f3-7d65781fd7d4/main — raw · history · blame

# How to do releases:

* Create a changeset with an update to `version.go`
 - this commit will be tagged
 - add another commit putting it back with '-dev' appended
* gpg sign the commit with an incremented version, like 'vX.Y.Z'
* Push the tag
* Create a "release" from the tag on github
 - include the binaries from `make build.arches`
 - write about notable changes, and their contributors
 - PRs merged for the release