čt 11. 6. 2015 v 11:25 odesílatel Matthias Wessendorf <matzew@apache.org> napsal:
Hi Stefan,

thanks for the tests!


On Thu, Jun 11, 2015 at 5:01 AM, Stefan Miklosovic <smikloso@redhat.com> wrote:
Hi,

I am mostly tracking what Tadeas found for Beta1 release.

1. While sending push notification from the browser, there is "No
variants" in variant selection by default. When I do not select any
variant, the message is sent to all variants. It should be renamed to
"All variants" instead "No variants" or it should be said that when
nothing is chosen, by default it will be sent everywhere.



See my reaction here: https://issues.jboss.org/browse/AGPUSH-1449?focusedCommentId=13077344&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13077344
 


 
2. For some reason there is a lot of space in the bottom and I can
scroll away all the content - minor issue.

Not sure I understand; bottom of where (and what browser)?
Mind filing a JIRA for this ? 

This should be fixed imo, @Andres worked on that. I was not able to reproduce is though and ?I'

 
Bugs:

1. After adding variant for simple push in the wizard, all links on
that variant page are dead - they do not do anything.


 
Hrm, worked for me (Chrome, incognito window). What browser did you use ?
 

UI/UX Quirks


4. This is not changed in beta 2 and I agree with Tadeas about it -
When hitting the Edit variant button, it shows a dialog where I can
change only the name of the variant. However when I click the Change
network options button, I am presented with the possibility to change
both the name of the variant and the network specific configuration. I
would therefore suggest to not show the name field in the Change
network options dialog as it is not considered a good practise to have
two ways of doing the same thing in UI.
 


 
I tried helloworld quickstart on Android tablet, pushes arrived
without problems, I reinstalled my notebook few days ago so you can
imagine that the bootstraping of all development tools and compilation
of all libs was not so straighforward however I have to say that it
was overall smooth experience and I did it at the first shot.

thanks, glad to hear. And yes, the tricky part is the 3rd party setup :-)
 

Admin UI is very nice and responsive as well and I like it as Tadeas
does. Whoever made the decision to migrate to new visual look&feel did
a good job. I excersised UI quite a lot and I do not encounter any
usability nor performance issue.

Andres drove the initiative w/ help from Lukas and?

I am overall satisfied with this release and I do not raise any
significant objections which would prevent the release of 1.1.0-beta.2
of UPS.

awesome, will click the button
 

I would like to see the release of UPS Java client 1.0.0.Beta2 as
well. Right now there is not any beta2-aligned sender to UPS
1.1.0-beta.2. Beta1 sender is using unifiedpush-push-model of version
1.0.0-alpha2 so I expect that Java client will use parent 0.2.15 and
all bits will be aligned properly.

fair point! This needs (and will be) to be fixed in Final.


Thanks again for the detailed report!

-Matthias
 

Regards

Stefan

On Wed, Jun 10, 2015 at 4:46 PM, Sebastien Blanc <scm.blanc@gmail.com> wrote:
> +1
>
> On Wed, Jun 10, 2015 at 4:45 PM, Matthias Wessendorf <matzew@apache.org>
> wrote:
>>
>> Hi,
>>
>> Stefan from our QE ask if we can delay the release to tomorrow,
>> test have been updated to beta.2 but he wants to web console and run some
>> demos.
>>
>> IMO this is fine
>>
>> On Fri, Jun 5, 2015 at 4:58 PM, Matthias Wessendorf <matzew@apache.org>
>> wrote:
>>>
>>> Hi team,
>>>
>>> here is the second beta release for the UPS 1.1.0. It contains more
>>> features and improvements around UI, Keycloak_1.2.0 (w/ enabled direct
>>> access grant) and a lot of other stuff:
>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578
>>>
>>> Please test the staged release:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5745/
>>>
>>> Like w/ the previous beta, please make sure you use a full profile
>>> WildFly or EAP server for tests, since we now have JMS hooks ;-)
>>> (See README for details)
>>>
>>> On Wednesday I'd like to press the button to release it to the wild.
>>>
>>> PS: For this beta release we won't yet be updating our Openshift
>>> cartridge - that will stay on 1.0.3 (stable) for a little longer time. For
>>> the next FINAL release in a few weeks we will get to this Openshift as well.
>>>
>>> -Matthias
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>
>>
>>
>>
>> --
>> 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



--
Stefan Miklosovic
Red Hat Brno - JBoss Mobile Platform

e-mail: smikloso@redhat.com
irc: smikloso
_______________________________________________
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