conserver/package
2020-10-18 23:41:46 -07:00
..
config.guess cache the config.* scripts and use them if we have trouble pulling them down 2019-03-29 16:52:22 -07:00
config.sub cache the config.* scripts and use them if we have trouble pulling them down 2019-03-29 16:52:22 -07:00
create-changes move get-version so it persists and autoreconf can be run with released version 2019-03-29 19:56:14 -07:00
make-and-stage-release fixing links to github repo - from conserver to bstansell 2020-10-18 23:41:46 -07:00
README.md note about a "local" build 2019-03-27 20:36:53 -07:00
run-gindent adding .gitignore and not removing ~ files 2019-03-21 01:20:56 -07:00
setup-configure cache the config.* scripts and use them if we have trouble pulling them down 2019-03-29 16:52:22 -07:00

Testing Locally

You can run ./package/make-and-stage-release local and the current code will be packaged into ./build so anyone can configure and build code in a confined space.

Creating a new release

  • Create a new release branch git checkout -b release-vx.y.z
  • Edit conserver/version.h
  • Update CHANGES with output of ./package/create-changes vx.y.z..
  • Double-check and merge release branch
  • Run GITHUB_TOKEN=xxxx ./package/make-and-stage-release to tag release, create distribution, pgp sign, and push to github

Requirements:

  • autoconf
  • githubrelease (pypi)
  • gpg

Publishing a release

  • Use github to promote from draft or use the command output from make-and-stage-release
  • Send announcement on mailing lists