Hey
I was wrong. We actually skip two steps in the testing process. Do not
test upgrading. Upgrading is now simply removing the old platform and
adding the new one. If you are using a standalone workflow, you should
probably migrate your changes over manually. Apologies for this, the
release
Hey
A reminder when testing, we have deprecated the update script for
standalone projects. Step 5 will most likely fail becuase we're changing
the structure. We've agreed to deprecate that script, since it has already
been deprecated for iOS and Windows.
https://github.com/apache/cordova-coho/b
StudioProjectCompat has been merged. I think we should start the release
process ASAP.
On Wed, Nov 29, 2017 at 2:36 AM, Jan Piotrowski
wrote:
> Thanks Joe and Darryl, makes sense and sounds good.
>
> I'm looking forward to the merge and getting some more eyeballs (and
> projects with all their
Thanks Joe and Darryl, makes sense and sounds good.
I'm looking forward to the merge and getting some more eyeballs (and
projects with all their different plugins...) on it. Having a "modern"
project structure is really great.
-J
2017-11-29 1:36 GMT+01:00 Darryl Pogue :
> I believe we can do pub
I believe we can do published beta or rc builds, so long as they are
considered releases and follow the usual rules for a published
release. They would be releases, but with a -beta.1 or -rc.1 suffix on
the version number.
We probably don't have to do that through: As Joe says, it's a major
versio
On Tue, Nov 28, 2017 at 3:35 PM, Jan Piotrowski
wrote:
> Is there any "beta" release process defined (7.0.0-beta?) that could
> be used to get more feedback? Maybe create a blog post with
> instructions on how to test this beta version?
> I can't even imagine all the variations on how people out
Is there any "beta" release process defined (7.0.0-beta?) that could
be used to get more feedback? Maybe create a blog post with
instructions on how to test this beta version?
I can't even imagine all the variations on how people out there are
using all this and what could go wrong.
-J
2017-11-2
Comments on the PR are good for a line-by-line. This e-mail thread is
basically to decide whether to go ahead with the release process, which is
indicated in excruciating detail here:
https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
I'll be merging this in tom
Thanks Darryl, seems I scrolled over the comments a bit too fast .
Just installed locally with cordova 7.1.0 and seems to work fine!
Here is a Github repo with what I did:
https://github.com/janpio/cordova-android7test
There are two branches you can compare:
https://github.com/janpio/cordova-a
The steps here should work:
https://github.com/apache/cordova-android/pull/389#issuecomment-320067936
To recap on email, you'll want to add the android platform via a git reference:
cordova platform add
git://github.com/infil00p/cordova-android.git#StudioProjectCompat
On Tue, Nov 28, 2017 at
Awesome!
For reference, you are talking about
https://github.com/apache/cordova-android/pull/389, correct?
What can I / one do to test this locally?
-J
2017-11-28 19:53 GMT+01:00 Joe Bowser :
> Hey
>
> I'm going to merge in StudioProjectCompat into Master today. Once that's
> done, I'd like to
Hey
I'm going to merge in StudioProjectCompat into Master today. Once that's
done, I'd like to get the next major version of Cordova out so that there's
not a crazy difference between master and the released versions of
Cordova. This release will have the new structure for Android Studio
project
12 matches
Mail list logo
