On Mar 13, 2014, at 1:11 PM, Matthias Wessendorf <matzew@apache.org> wrote:




On Thu, Mar 13, 2014 at 6:09 PM, Burr Sutter <bsutter@redhat.com> wrote:
By the way, I am really enjoying the new Test Message feature :-)

IT's not only a test message :) 
you can use that to just reach out to users :) (think marketing apps :) ) 

Well, I do not yet consider it ready for marketing users. Mostly because of the security model - everybody is an admin - it would be bad if the marketing folks messed up the iOS cert for example.

I believe we should have some form of read-only user role as well as a "message sending" only role - therefore the admin can protect all the other settings.  

This can wait until after 1.0, for now, just "push administrators" can send messages - useful for testing, sometimes in the case of emergency, however, I would not recommend giving all that power to the average marketing person.

 

curl is a pain and becomes problematic for our Windows userbase anyway.


On Mar 13, 2014, at 12:59 PM, Sebastien Blanc <scm.blanc@gmail.com> wrote:

Deployed and tested with success !! 
+1 



On Wed, Mar 12, 2014 at 6:19 PM, Matthias Wessendorf <matzew@apache.org> wrote:
FYI:   On IRC Stefan reported the WAR from my staging repo also passes the tests.






On Wed, Mar 12, 2014 at 4:39 PM, Matthias Wessendorf <matzew@apache.org> wrote:



On Wed, Mar 12, 2014 at 4:35 PM, Stefan Miklosovic <smikloso@redhat.com> wrote:




On Wed, Mar 12, 2014 at 3:48 PM, Stefan Miklosovic<smikloso@redhat.com> wrote:
Hello Matthias,

we executed UPS integration tests on the latest commit in 0.10.x brach
(35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok.


awesome!

Since you talked about Bintray, we could move this little bit further and test
staged bits directly from there - meaning wars which are not on Maven Central
yet but they are already on Bintray would be downloaded from there dynamically
and our intergration test suite would be run directly against built (but yet unreleased) wars.


the WAR files from my private staging repo will be exactly those that I upload to bintray;

I use the private repo, to avoid an early publish (before the release is really done)
Ah, right. The discussion I had with Karel was that it would be nice to test these built wars before they 
finally reach Maven Central and Bintray would act as a staging place just as your private repo right now.


feel free to use my private staging repo as your repo (it's a valid maven repo URL)

 

I am not sure if Bintray supports this but if it is possible, Bintray could be exactly what your
"private repo" is right now, we would just make it more robust / official moving from
your private repo somewhere (no offence) to Bintray.

By doing this, we kind of abuse Bintray, I guess it is not primarily used for staging bits but for announcing them to the world,
however it is technically possible.

yes, but I am more interested in keep my current process:

* staging: my Apache account
* release: bintray (there we have all the good stats etc)
 

However feel free to cancel this idea. We are planning to test these unreleased wars anyway so instead of Bintray 
we try to download them from your private repo but I am just saying that having it from Bintray seems to be better.

And again, these files from my private repo are exactly the same that I than upload to bintray (assuming the release tests are passing)

-M
 

- Stefan

-Matthias

In other words, Bintray could be used as a staging facility for UPS.

WDYT?

Stefan Miklosovic
Red Hat Brno - JBoss Mobile Platform

e-mail: smikloso@redhat.com
irc: smikloso

Hello,

for the upcoming release we have a few, but important, tickets solved:


Before finishing the release, let's see if there are issues w/ the server, hence I have staged the WAR file on my private webspace:




If they aren't any objections or remarks I will release the bits to bintray on Friday morning


Greetings,
Matthias

-- 
Matthias Wessendorf 

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Matthias Wessendorf 

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Matthias Wessendorf 

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Matthias Wessendorf 

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev