Regardless of the answer to this question. I will review the RC and provide
my input.

signatures are all good, same with hash signatures

lmcgibbn@LMC-032857 /usr/local/ug(master) $ gpg --import KEYS
gpg: key 17AA5B25: public key "David Johnson <[email protected]>"
imported
gpg: Total number processed: 1
gpg:               imported: 1
lmcgibbn@LMC-032857 /usr/local/ug(master) $ gpg --verify
KEYS
apache-usergrid-incubating-1.0.0-rc3-source.tar.gz.md5
apache-usergrid-incubating-1.0.0-rc3-source.zip.md5
apache-usergrid-incubating-1.0.0-rc3-source.tar.gz
apache-usergrid-incubating-1.0.0-rc3-source.zip
apache-usergrid-incubating-1.0.0-rc3-source.tar.gz.asc
apache-usergrid-incubating-1.0.0-rc3-source.zip.asc
lmcgibbn@LMC-032857 /usr/local/ug(master) $ gpg --verify
apache-usergrid-incubating-1.0.0-rc3-source.tar.gz.asc
gpg: Signature made Tue Aug 26 11:08:50 2014 PDT using DSA key ID 17AA5B25
gpg: Good signature from "David Johnson <[email protected]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 0972 6369 9A89 2BBB 188E  1E39 FD9E D9F1 17AA 5B25
lmcgibbn@LMC-032857 /usr/local/ug(master) $ gpg --verify
apache-usergrid-incubating-1.0.0-rc3-source.zip.
apache-usergrid-incubating-1.0.0-rc3-source.zip.asc
apache-usergrid-incubating-1.0.0-rc3-source.zip.md5
lmcgibbn@LMC-032857 /usr/local/ug(master) $ gpg --verify
apache-usergrid-incubating-1.0.0-rc3-source.zip.asc
gpg: Signature made Tue Aug 26 11:08:48 2014 PDT using DSA key ID 17AA5B25
gpg: Good signature from "David Johnson <[email protected]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 0972 6369 9A89 2BBB 188E  1E39 FD9E D9F1 17AA 5B25
lmcgibbn@LMC-032857 /usr/local/ug(master) $ md5
apache-usergrid-incubating-1.0.0-rc3-source.zip
MD5 (apache-usergrid-incubating-1.0.0-rc3-source.zip) =
5fbf5acc955efedde2474690ec0ada62
lmcgibbn@LMC-032857 /usr/local/ug(master) $ md5
apache-usergrid-incubating-1.0.0-rc3-source.tar.gz
MD5 (apache-usergrid-incubating-1.0.0-rc3-source.tar.gz) =
ae155b87554d1254410857902f113853

So I then unzip the .zip to find that the resulting artifact is actually
called apache-usergrid-incubating-1.0.0-rc3
Is this an issue for you guys? I find this a bit strange. Does this cause
confusion for people further down the line? It is already causing confusion
for me right now. I am not really sure why it is not just called
apache-usergrid-incubating-1.0.0. The same is true for the tar.gz

I then go in to portal and run ./build.sh e2e, this is what I get

lmcgibbn@LMC-032857
/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal(master) $
./build.sh e2e
...
Done, without errors.
./build.sh: line 31: webdriver-manager: command not found
to run e2e tests you need to have a running instance of webdriver, 1) npm
install protractor -g -> 2) webdriver-manager start --standalone
Running "connect:e2e-chrome" (connect) task
Started connect web server on 127.0.0.1:3006.

Running "protractor:chrome" (protractor) task
Using the selenium server at http://localhost:4444/wd/hub

/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1702
      throw error;
            ^
Error: ECONNREFUSED connect ECONNREFUSED
    at ClientRequest.<anonymous>
(/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/node_modules/selenium-webdriver/http/index.js:128:16)
    at ClientRequest.emit (events.js:95:17)
    at Socket.socketErrorListener (http.js:1547:9)
    at Socket.emit (events.js:95:17)
    at net.js:440:14
    at process._tickCallback (node.js:419:13)
==== async task ====
WebDriver.createSession()
    at Function.webdriver.WebDriver.acquireSession_
(/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:131:49)
    at Function.webdriver.WebDriver.createSession
(/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:111:30)
    at Builder.build
(/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/node_modules/selenium-webdriver/builder.js:106:20)
    at HostedDriverProvider.getDriver
(/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/lib/driverProviders/hosted.dp.js:54:9)
    at
/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/lib/runner.js:383:35
    at _fulfilled
(/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/node_modules/q/q.js:797:54)
    at self.promiseDispatch.done
(/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/node_modules/q/q.js:826:30)
    at Promise.promise.promiseDispatch
(/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/node_modules/q/q.js:759:13)
    at
/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/portal/node_modules/protractor/node_modules/q/q.js:525:49
>>
Fatal error: protractor exited with code: 8

The Admin Portal has been built and delivered to /dist
deploy the contents directory to your webserver
or run it now using the following command:
grunt dev

Happy Usergriding!


I then go into /release, immediately I spot a sign-release.sh script. Is
this meant to be here?

I run
lmcgibbn@LMC-032857
/usr/local/ug/apache-usergrid-incubating-1.0.0-rc3/release(master) $ mvn
install

I get a successful build however EVERYTHING is labelled as
apache-usergrid-incubating-1.0.0-rc3.

I then go into /sdks
Immediately I see a 'new' sdk usergrid-java-sdk-0.0.6 in addition to the
existing java sdk. is this meant to be here?
I install both Android and Java SDK... all OK. I am not going to try each
one... but this would be really helpful to see each one build and test
successfully.

I then go into /stack
I go mvn clean install
One thing I notice about the build output is that it seems to be jam packed
with stack traces. So I file
https://issues.apache.org/jira/browse/USERGRID-222
Eventually the build fails as follows

...
Tests in error:
  OrganizationIT.testCreateOrganization:83 ยป UnconfirmedAdminUser

Tests run: 98, Failures: 0, Errors: 1, Skipped: 3

[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Usergrid Parent ................................... SUCCESS [  2.188
s]
[INFO] Usergrid Java SDK 0.0.3 ........................... SUCCESS [  1.313
s]
[INFO] Usergrid Build Tools .............................. SUCCESS [  0.143
s]
[INFO] Usergrid Config ................................... SUCCESS [  0.200
s]
[INFO] Usergrid Test Utils ............................... SUCCESS [  7.611
s]
[INFO] Usergrid Core ..................................... SUCCESS [05:06
min]
[INFO] Usergrid Services ................................. FAILURE [ 53.342
s]
[INFO] Usergrid MongoDB Emulator ......................... SKIPPED
[INFO] Usergrid REST ..................................... SKIPPED
[INFO] Usergrid Tools .................................... SKIPPED
[INFO] Usergrid Websocket ................................ SKIPPED
[INFO] Usergrid Launcher ................................. SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 06:11 min
[INFO] Finished at: 2014-08-28T23:35:16-08:00
[INFO] Final Memory: 59M/648M
[INFO]
------------------------------------------------------------------------

I also find a rat.txt within /stack/target, is this meant to be here?

I then dive into /ugc and execute gem install ugc
I can install it absolutely fine. I can then mess around and do stuff but I
haven't actually create an application that I can remeber so I stop there.

Honestly, the main problem I have here is with item 2.1 on the checklist
[0]. This is of course
2.1 Build is successful including automated tests. The expanded source
archive is expected to build and pass tests
<http://www.apache.org/dev/release.html#what-must-every-release-contain>. I
am not sure that this is the case. I would like for Dave to try and respond
to some of these issues but in all honesty I am also happy to give my +0 on
this one. I think that a lot of work has gone into this release candidate.
This includes lather, rinse, repeating for many of the community here...
which has to be praised and consideration given when we are pushing for our
first incubating release.

Thanks for rolling this snoopdave, you friggin rock.
Lewis

[0] http://incubator.apache.org/guides/releasemanagement.html#check-list


On Thu, Aug 28, 2014 at 2:46 PM, Lewis John Mcgibbney <
[email protected]> wrote:

> Hi Dave,
>
> KARMA for keeping this moving.
>
> On Tue, Aug 26, 2014 at 11:24 AM, <
> [email protected]> wrote:
>
>>
>>
>> Subject: [VOTE] Release 1.0.0-rc3 as Apache Usergrid 1.0
>> I have addressed each of the issues that Jake raised about the release and
>> believe we are ready to start a new vote for releasing Usergrid 1.
>>
>> You can find the release files for Apache Usergrid (incubating) 1.0.0-rc3
>> here:
>>     http://people.apache.org/~snoopdave/usergrid/
>>
>> The vote will remain open for 72 hours starting now.
>>
>>
> So a question which I haven;t seen anyone else ask.
> Are we not pushing Maven (for Java, Android) or any other 'more
> consumable' artifacts for the suite of SDK's?
> This is merely an observation and I think that it isprobably something we
> can invest in an dbuild into the release procedure in future releases.
> Thanks
> Lewis
>



-- 
*Lewis*

Reply via email to