I'm over due for this vote since I've been playing with docker containers, 
automating the build/testing process and flying all over the place... but:

Completed the test cases for the following built from the latest available 
sources of each dependent library:
    name: Linux
    release: 3.16.0-4-amd64
    version: #1 SMP Debian 3.16.39-1 (2016-12-30)
    machine: x86_64

    openssl: "1.1.0g"
    openldap: "2.4.45"
    apr: "1.6.3"
    apr-util: "1.6.1"
    iconv: "1.2.2"
    brotli: "1.0.1"
    nghttp2: "1.27.0"
    zlib: "1.2.11"
    pcre: "8.41"
    libxml2: "2.9.7"
    php: "5.6.32"
    lua: "5.3.4"
    curl: "7.56.1"

As a side note, I'm experimenting with ways to capture build and test output as 
well as relevant system info related to a tested version of httpd. Here's the 
current format I am using in YML (can be seen here for this build: 

Feedback on anything else I should be capturing is welcome. This is the only 
surviving artifact of the build and test since it's all done in ephemeral 
docker containers.

On 2017-11-07 20:36, Daniel Ruggeri <drugg...@primary.net> wrote: 
> Hi, all;
>    Please find the proposed 2.5.0-alpha release tarballs and signatures
> at the following location. This release candidate was tagged from trunk
> as of r1814469:
> https://dist.apache.org/repos/dist/dev/httpd/
> I'd like to call a vote to release this alpha candidate. Please do note
> - this is my first attempt at cutting a release and mistakes are likely.
> Therefore, I'll let the vote run at least 10 days (possibly more as I
> will be traveling to Dublin next week) and will greatly appreciate any
> additional scrutiny the release tarball can be given.
> Some notes to share after having executed the process for the first time:
> * I'm not 100% sure on the proper syntax for an alpha candidate with the
> release.sh[1] script. I used "./release.sh --tag 2.5.0-alpha alpha
> httpd-2.5 2.5.0 'drugg...@primary.net". This seems to have produced
> desired results.
> * I created two scripts[2] to automate the tagging of SVN and minor file
> modifications associated with a release as well as the push of the
> tarballs/signatures to the repo mirror. Unfortunately, I lack the karma
> to commit to site/trunk. How do I obtain this karma?
> * I'd like to make some updates to the documentation[3] about how to
> produce releases to point out the existence of the new scripts and make
> the process more clear. Same note about karma to site/ applies.
> * The documentation mentioned to AP_SERVER_DEVBUILD_BOOLEAN to 0 for the
> tagged release. I assume this still holds true for an alpha release.
> * Blockers for automation really only seem to live around credential
> management (svn password and keyring passphrase) and the conducting of
> the vote itself over email. Kudos to everyone involved for putting
> together the scripting that already exists!
> * I'd like to create yet another script that does a pre-flight check for
> a machine to ensure that the host it is run on has the dependencies all
> of the above scripts need. Thing is, other than java for the docs build
> and gpg... I'm not sure what those other things may be (or even if there
> are any). Pointers welcome.
> [1] http://svn.apache.org/repos/asf/httpd/site/trunk/tools/release.sh
> [2] http://people.apache.org/~druggeri/scripts/
> [3] http://httpd.apache.org/dev/release.html
> P.S.
> I'll be in Dublin next week if anyone would like to catch up!
> -- 
> Daniel Ruggeri

Reply via email to