couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From janl <>
Subject [GitHub] couchdb pull request: Add first stab at a release build script.
Date Wed, 11 Feb 2015 23:09:04 GMT
GitHub user janl opened a pull request:

    Add first stab at a release build script.

    Creates a release directory `apache-couchdb` that we can wrap in a tarball. This is a
quick hack to discuss whether this direction is anything we’d like to go towards for releases.
    Please be generous with feedback, thank you! :)
    make release
    cd apache-couchdb
    make dist
    ./rel/couchdb/bin/couchdb # starts CouchDB
    End users will download apache-couchdb-$vsn.tar.gz and then:
    tar xzf apache-couchdb-$vsn.tar.gz
    cd apache-couchdb-$vsn
    make dist
    This builds fauxton and the docs as part of `make release`, so that end users don’t
have to build those themselves.
    Preliminary Todo:
     - [ ] infer CouchDB version from source tree and use in tarball, fauxton and welcome
     - [ ] fix bug noted in build-aux/ where cloning the current branch
doesn’t work when a version tag is specified
     - [ ] make docs build understand that it doesn’t have to re-build if targets already
     - [ ] actually create tarball
     - [ ] add `make install` target
     - [ ] Windows version
     - [ ] test test test
    Again, please be generous with feedback!

You can merge this pull request into a Git repository by running:

    $ git pull build

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #302
commit c2d2f7e44b7031c6ffaa985c8c33c42aa18affe8
Author: Jan Lehnardt <>
Date:   2015-02-11T21:24:58Z

    Add first stab at a release build script.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message