incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <>
Subject Re: [VOTE] Release ManifoldCF 0.2-incubating, RC2
Date Mon, 09 May 2011 08:34:15 GMT
Hi - just to clarify, we did not include the HTTPD extension in the
release, but it remains available in source control for backwards
compatibility.  Most people use the Active Directory Authority at the
moment.  But thank you for compiling it.

As for the RAT report, the skins question is known and a ticket is
open for that.  The other files are temporary files resulting from
your test run and I will open a ticket to exclude those from the
rat-source target.

We've still received zero binding evaluations from incubator for this
release, FWIW.


On Sun, May 8, 2011 at 4:15 PM, Marvin Humphrey <> wrote:
> On Thu, May 05, 2011 at 12:57:03PM -0400, Karl Wright wrote:
>> Just to be clear, the ManifoldCF podling needs incubator consideration
>> of the release candidate in order to do the release, and three binding
>> +1 votes.  Any chance that this might happen?
> Since I'm only a podling committer and not an Incubator PMC member, I can't
> offer a binding vote.  Nevertheless, I've performed some superficial QC on the
> release candidate.
>  * All signatures and sums check out, including for the binary artifacts.
>  * "ant test" succeeds on the expanded src.tar.gz tarball on my OS X laptop.
>  * The HTTPD extension builds after a Makefile hack (explained below).
>  * "ant clean" properly cleans up after "ant test".
>  * There's a problem with line endings in the src.tar.gz archive.
> The HTTPD module, mod_authz_annotate, built successfully, but only after I
> hacked the Makefile to use "apxs" instead of "apxs2".  Not a blocker, IMO, but
> now you know. :)  Also, neither "make clean" nor "ant clean" cleans up all
> build detritus -- these got left behind:
>    mod_authz_annotate.lo
>    mod_authz_annotate.o
>    mod_authz_annotate.slo
> I was surprised to find that most of the text files in the src.tar.gz have
> Windows line endings.  That's ugly, but not a blocker IMO.  It looks like they
> have the proper settings in Subversion -- e.g. for README.txt, svn:eol-style
> is "native" -- so it seems the problem arose because the tar.gz package was
> prepared on a Windows box.  Maybe try preparing the tar.gz on something
> unixish in the future.
> Lastly, I ran "ant rat-sources", and though it declared "BUILD SUCCESSFUL",
> RAT flagged 8 files:
>    connectors/filesystem/test-output-postgresql/logging.ini
>    connectors/filesystem/test-output-postgresql/manifoldcf.log
>    connectors/filesystem/test-output-postgresql/properties.xml
>    framework/test-output-postgresql/logging.ini
>    framework/test-output-postgresql/manifoldcf.log
>    framework/test-output-postgresql/properties.xml
>    site/src/documentation/skins/common/xslt/html/split.xsl
>    site/src/documentation/skins/lucene/note.txt
> I'd suggest presenting a clean RAT report next time you call a vote on an RC to
> make things easier on everybody.
> Hope this helps,
> Marvin Humphrey
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message