Hi Team,
Does anyone have any reason to delay a cordova-android@10.1.2 release?
Any outstanding patches to land?
If not, I will start the release in the upcoming days.
Notable fixes:
- Fixes for Java 11 (https://github.com/apache/cordova-android/pull/1406)
- Fixes for escaped characters in Ap
hink we should
> discuss this but outside of this release.
>
> I think we can continue with the release. In fact, I am ready to push the
> VOTE. :)
>
>
>
>
> From: Brody Chris
> Reply: dev@cordova.apache.org
> Date: February 13, 2019 at 10:39:00
> To: dev@cord
: Re: [DISCUSS] Cordova-Android Release
A couple followup items:
* I suspect we should update the documentation as well
* I think it would be good if we could deprecate
android-targetSdkVersion, android-maxSdkVersion, and maybe some
related items in config.xml, as I had loosely implied on GitH
much more.
> >
> >
> >
> > From: Brody Chris
> > Reply: dev@cordova.apache.org
> > Date: February 13, 2019 at 8:13:23
> > To: dev@cordova.apache.org
> > Subject: Re: [DISCUSS] Cordova-Android Release
> >
> > I would definitely agree
cordova.apache.org
> Date: February 13, 2019 at 8:13:23
> To: dev@cordova.apache.org
> Subject: Re: [DISCUSS] Cordova-Android Release
>
> I would definitely agree that we should do it right and get rid of
> project.properties, along with the other Eclipse artifacts. I already
> raised issu
, Adaptive Icons, and much more.
From: Brody Chris
Reply: dev@cordova.apache.org
Date: February 13, 2019 at 8:13:23
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Cordova-Android Release
I would definitely agree that we should do it right and get rid of
project.properties, along with the
I would definitely agree that we should do it right and get rid of
project.properties, along with the other Eclipse artifacts. I already
raised issues on GitHub to get rid of project.properties and other
artifacts from Eclipse.
I think none of us have the extra time to go through the needed
cleanu
On Tue, Feb 12, 2019 at 2:47 PM Chris Brody wrote:
> [...]
> The easy solution to bug 666 would be to revert PR 664, which would
> consequently reintroduce cordova-android bug 629. I would favor
> resolving it by reading the default targetSdkVersion value from
> project.properties, as briefly disc
We are now down to the following:
* https://github.com/apache/cordova-android/pull/655 for which I just
limited the scope as discussed on GitHub
* https://github.com/apache/cordova-android/issues/666 where I listed
some alternative solutions
The easy solution to bug 666 would be to revert PR 664,
I think we are almost ready for cordova-andropid@8.0.0 release, should
finish the following:
* review and merge the following proposed PRs:
- https://github.com/apache/cordova-android/pull/656
- https://github.com/apache/cordova-android/pull/663
- https://github.com/apache/cordova-android/pu
I think it would be a pretty bad reflection on Apache Cordova if we
would announce a new release that is known to depend on deprecated
platform behavior. Not supporting AndroidX would be a prime example. I
think it would also be pretty bad if a bug such as bug 508 would be
introduced in the middle
Let me correct my question then:
Why are those blocking and can not be added in a future major
cordova-android release (with an accompanying CLI release that adds
this as the new default android version to be installed if that is
still necessary) when those changes are merged?
-J
Am Fr., 8. Feb.
Unless we find a way of enabling/disabling Android X support, it's going to
be a breaking change for all plugins using using the old way, so we can't
do that in a 8.1 release
El vie., 8 feb. 2019 a las 12:03, Jan Piotrowski ()
escribió:
> I am not sure I follow:
> Why are those blocking and can n
I am not sure I follow:
Why are those blocking and can not be added with a quick 8.1 when
those changes are merged?
-J
Am Fr., 8. Feb. 2019 um 01:55 Uhr schrieb Chris Brody :
>
> I think the major blockers are AndroidX and bug 508. I already
> proposed a quick fix solution for 508. For AndroidX I
I think the major blockers are AndroidX and bug 508. I already
proposed a quick fix solution for 508. For AndroidX I think we need to
do a little more analysis and testing.
Unfortunately I cannot promise much on my part due to some other
priorities. I will try to take another look in the next few
Update coming later today. I think there are still a number of
blockers that we need to get resolved.
On Thu, Feb 7, 2019 at 3:48 AM Bryan Ellis wrote:
>
> Can I get an update on this?
> Is there anyone still working on any blockers that need to be finished
> before release?
> Can we continue wit
Can I get an update on this?
Is there anyone still working on any blockers that need to be finished
before release?
Can we continue with this release?
On Sat, Jan 19, 2019 at 6:49 AM Chris Brody wrote:
> I would agree with Julio that we should verify androidx support before we
> finish the next
I would agree with Julio that we should verify androidx support before we
finish the next major release. I don't expect we will have to make any
fixes on cordova-android for androidx support. Issues for reference:
* https://github.com/apache/cordova/issues/69
* https://github.com/apache/cordova-and
As it's going to be a major release, I think we should look a bit more into
Android X before doing a major release, just in case we need to do major
changes.
In the issue related to Android X, I commented that we didn't have the
gradle.properties file, but in the linked PR I saw it's going to be
ge
I am investigating a quick solution for the bug, hope to have something
today.
On Fri, Jan 18, 2019, 8:42 AM Chris Brody The bug was introduced by new code that was added to both master and 7.1.4.
>
> On 7.1.4 the issue is discussed in:
> https://github.com/apache/cordova-android/issues/599
>
> I
The bug was introduced by new code that was added to both master and 7.1.4.
On 7.1.4 the issue is discussed in:
https://github.com/apache/cordova-android/issues/599
I hope we can find a quick solution before we make the new release.
Fixing the bug would introduce some kind of change in behavior,
Is this a new bug introduced by the new code that would be released?
If not, there is no reason to stop a release of that (good) code. As
soon as a fix for this bug is available, we can release it as a follow
up release (patch, minor, major - whatever appropriate).
-J
Am Fr., 18. Jan. 2019 um 13:
I do not think we should make a new cordova-android release before we can
resolve https://github.com/apache/cordova-android/issues/508
I think it is a pretty bad bug. I would be happy to explain further if
needed.
On Fri, Jan 18, 2019 at 12:56 AM Bryan Ellis wrote:
> Does anyone have any reason
Does anyone have any reason to delay a cordova-android platform release?
Any outstanding patches to land?
If not, I will start the release process shortly.
Please review the blog post: https://github.com/apache/cordova-docs/pull/789
On Tue, Feb 20, 2018 at 2:05 PM, Joe Bowser wrote:
> +1
>
> On Feb 20, 2018 9:19 AM, "Jan Piotrowski" wrote:
>
> > +1 Looking good.
> >
> > 2018-02-20 19:53 GMT+01:00 Steven Gill :
> > > Issue: https://issues.apache.or
+1
On Feb 20, 2018 9:19 AM, "Jan Piotrowski" wrote:
> +1 Looking good.
>
> 2018-02-20 19:53 GMT+01:00 Steven Gill :
> > Issue: https://issues.apache.org/jira/browse/CB-13912
> >
> > I'm thinking minor bump to 7.1.0. You can see the change log in the
> > comments of the issue
> >
> > On Sat, Feb
+1 Looking good.
2018-02-20 19:53 GMT+01:00 Steven Gill :
> Issue: https://issues.apache.org/jira/browse/CB-13912
>
> I'm thinking minor bump to 7.1.0. You can see the change log in the
> comments of the issue
>
> On Sat, Feb 17, 2018 at 1:51 PM, Simon MacDonald
> wrote:
>
>> +1
>>
>> The change
Issue: https://issues.apache.org/jira/browse/CB-13912
I'm thinking minor bump to 7.1.0. You can see the change log in the
comments of the issue
On Sat, Feb 17, 2018 at 1:51 PM, Simon MacDonald
wrote:
> +1
>
> The change is super useful for Android 4.4 devices.
>
> On Fri, Feb 16, 2018 at 17:48
Meh, ignore please. I messed up the title :(
2018-02-19 16:57 GMT+01:00 Jan Piotrowski :
> Does anyone have any reason to delay a cordova-android platform release?
> Any outstanding patches to land?
>
> If not, I will start the release soon-ish.
---
Does anyone have any reason to delay a cordova-android platform release?
Any outstanding patches to land?
If not, I will start the release soon-ish.
-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional comm
+1
The change is super useful for Android 4.4 devices.
On Fri, Feb 16, 2018 at 17:48 gandhi rajan wrote:
> +1
>
> On Saturday, February 17, 2018, Steven Gill
> wrote:
>
> > cordova-android release. Going to do a minor or patch release for
> android.
> > Any issues or concerns?
> >
>
>
> --
> R
+1
On Saturday, February 17, 2018, Steven Gill wrote:
> cordova-android release. Going to do a minor or patch release for android.
> Any issues or concerns?
>
--
Regards,
Gandhi
"The best way to find urself is to lose urself in the service of others !!!"
+1
2018-02-16 19:37 GMT+01:00 Steven Gill :
> cordova-android release. Going to do a minor or patch release for android.
> Any issues or concerns?
>
cordova-android release. Going to do a minor or patch release for android.
Any issues or concerns?
34 matches
Mail list logo
