I have created a new release candidate that satisfies all of the items that
Jake raised about RC1, but I'm not ready to call for a vote yet.

The issues Jake raised:

   - no checksum hashes provided
   - source archive filename does not start with apache or contain
-incubation
      - rc source archive filename should contain -rc#
   - binary files included in source archive
   - no DISCLAIMER file included
   - files missing Apache license header (ack -L "Apache Software
Foundation")

To fix those issues I had to take these steps:

   - Add Usergrid SDK 0.0.3 source code, for the REST tests
   - Add Usergrid SDK 0.0.6 source code, for the Android SDK
   - Removed all jars from stack, Java SDK and Android SDK
   - Removed generated Javadoc from Java SDK and Android SDK
   - Add md5 step to the sign-release.sh script
   - Change the name of the release file in the release assembly
   - Add ASF header to about 100 files, mostly in SDKs
   - Remove Selenium driver and jar from Portal

I'm not ready to call for a vote yet because I worry that we may still have
some quibbles about missing headers in some files. I used a command like
this to get a list of the files that are missing headers:

ack -L "Apache Software Foundation" | grep -v "target" | grep -v
bower_components | grep -v dist | grep -v META-INF | grep -v "js/libs" |
grep -v "\.json" | grep -v "\.md" | grep -v "\.txt" > nolicense.txt

Jake: does the header situation look good in the new RC?

Also, I'm concerned that removing the Selenium driver and jar may cause
parts of our Portal tests to fail. One of the requirements for release is
that our code builds and tests pass, so we need to address this (even if it
means excluding the Portal tests).

Rod, Shawn and other Portal guys: thoughts on Selenium?

The new RC is here:
   http://people.apache.org/~snoopdave/usergrid/

Thanks,
Dave

Reply via email to