Hi Matthias, to make it easy to our scripts and being selfish, Docker.
Do you think that's possible to have our artifacts named with the suffix
"-latest.tar.gz" at bintray for example?
Something like:
auth-server-latest.tar.gz
ups-server-latest.tar.gz
On 2014-08-07, Matthias Wessendorf wrote:
Hi team,
a little update
On Wed, Aug 6, 2014 at 5:07 PM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
> Hi team,
>
>
> now that keycloak-beta4 was released, we have an updated PR from abstractj
> to use that version ([1]), combined w/ an upcoming release of our parent
> (to leverage the kc-beta4 JARs), see [2].
>
> At the moment we have a few open PRs:
>
https://github.com/aerogear/aerogear-unifiedpush-server/pulls
>
> Please review, but DO NOT merge them! Why? The KC PR goes in first,
> afterwards I will merge the other items, based on review feedback.
>
> By tomorrow that all should be done (read: merged) and there will be a
> staged repo for tests (and openshift updates), watch out for the email!
>
The staging will happen early Friday morning (German time), mainly to allow
us a smooth finish of the on-going testing and review of the last two PRs.
We are really close! YAY! team++
> As mentioned on IRC, the nominees for the testing, are:
> * sblanc, cvasilak, dbevenius, lholmquist, lfryc and abstractj
>
sblanc is out the next two weeks - we will find someone else :-)
-Matthias
>
> Besides testing the UPS staging repo, please test our quickstarts
> (including their client SDKs) as well:
> *
https://github.com/aerogear/aerogear-push-helloworld
> *
https://github.com/aerogear/aerogear-push-quickstarts
>
> (use the master branch - there will be a .Beta2 TAG, if all goes well
> there)
>
> Last but not least, please 'test' the documentation as well. For instance
> the new UPS guide:
>
http://staging.aerogear.org/docs/unifiedpush/ups_userguide/
>
> or other items of the new 'UPS doc center' :-)
>
http://staging.aerogear.org/docs/unifiedpush
>
>
> Hopefully, by Wednesday we have an awesome 1.0.0.Beta2 and shortly after
> that we can go to CODE_FREEZE for the 1.0.0.Final
>
> Any thoughts ?
>
> -Matthias
>
> PS: others, besides the nominated folks, are welcome to test the things as
> well :)
>
>
> -Matthias
>
> [1]
http://lists.jboss.org/pipermail/aerogear-dev/2014-August/008658.html
> [2]
http://lists.jboss.org/pipermail/aerogear-dev/2014-August/008672.html
>
>
> On Fri, Aug 1, 2014 at 6:35 AM, Matthias Wessendorf <matzew(a)apache.org>
> wrote:
>
>> Hi team,
>>
>> based on [1] I thought about our release timelines until 1.0.0.Final, and
>> shortly after.
>>
>> -
>>
>> 1.0.0.Beta2
>>
<
https://issues.jboss.org/browse/AGPUSH/fixforversion/12325092/?selectedTa...;:
>> 07/Aug/14
>>
>> This needs to include Keycloak-beta4, and might slip by one day, but not
>> much more of a delay.
>>
>
>
> --
> 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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev