In such case, would it make sense to lock Cordova related versions in
our tutorials/quickstarts/documentation and update versions there after
security bug instead?
On Tue, Aug 5, 2014 at 10:26 AM, Erik Jan de Wit <edewit(a)redhat.com>
wrote:
We had this discussion before and I still feel that this course of
action is wrong. It’s like let’s update the java library that we
created when there is a security error in java.
All people have to do is to use the newer version of the android
platform (if they are currently using 3.5.0)
cordova platform add android(a)3.5.1
On 5 Aug,2014, at 10:04 , Karel Piwko <kpiwko(a)redhat.com> wrote:
> +1 for updating.
>
> On Tue, Aug 5, 2014 at 8:45 AM, Matthias Wessendorf
> <matzew(a)apache.org>
> wrote:
>> FYI
>>
>>
https://twitter.com/apachecordova/status/496418463666028545
>>
>> Wondering, should we update the plugin ?
>>
>> --
>> 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