Sorry to say, but this source archive in its current state is not ready for release, my vote is a -1.
After starting to walk the release checklist I quickly hit the following areas (all prior to attempting the build/verify steps). These are all very common misses when packaging the first release under the ASF and nothing that should involve days to resolve. -Jake - 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") Apache Usergrid 1.0-RC0 checklist ----- ** 1.1 Checksums and PGP signatures are valid. 2.1 Build is successful including automated tests. ** 3.1 DISCLAIMER is correct, filenames include "incubating". 3.2 Top-level LICENSE and NOTICE are correct for each distribution. ** 3.3 All source files have license headers where appropriate. 3.4 The provenance of all source files is clear (ASF or software grants). 3.5 Dependencies licenses are ok as per http://apache.org/legal/ ** 3.6 Release consists of source code only, no binaries. On Fri, Aug 22, 2014 at 1:08 PM, Rod Simpson <[email protected]> wrote: > Usergriders, > > I am excited to send this email, which is a vote to release Usergrid 1.0. > I know everyone has been working really hard to make this happen and we > really appreciate everyone’s efforts!! > > This release is a source-code only release. We have plans to improve the > overall usability, but providing binaries and such. But for now, just > getting the source code out the door will be a major accomplishment. > > To my knowledge, we have completed all steps in the release process (prior > to the vote and actual release). > > Release files are located here: > http://people.apache.org/~snoopdave/usergrid/ > > I’ll be holding the voting through the end of Sunday to give people the > full weekend to test if they wish. If anyone is aware of problems that > shouldn’t be postponed, please report back as soon as possible. > > Also, please be careful with commits to Master until the vote is closed > and the > artifacts are released. The build has been tagged, but if we have to make > changes, additional commits could make this process more difficult. > > The user community is also encouraged to test this release candidate and > let us know of problems that they find. > > To start the voting, here is my +1. > > Thanks everyone! > > Rod > > > -- > Rod Simpson > @rockerston > rodsimpson.com
