You might go slow on this - somewhere in the back of my head I have
_something_ why we did not follow through with this in the past but I can
not figure out what it was, sorry :/ Hopefully it is nothing and will just
work.
J
Am So., 30. Aug. 2020 um 19:55 Uhr schrieb Tim Brust :
> Hi there,
>
> and it would help us to keep the issues and discussions all in one place.
I would challenge you actually want that. To be able to properly work on
one plugin, you would need to have labelled all issues and PRs and then
filter all views for that.
In my experience this only makes sense for
+1
Am Di., 18. Aug. 2020 um 08:31 Uhr schrieb Tim Brust :
> +1
>
> Sent from my iPhone
>
> > On 18. Aug 2020, at 8:22 AM, Dave Alden wrote:
> >
> > +1
> >
> >> On Tue, 18 Aug 2020, 05:47 Bryan Ellis, wrote:
> >>
> >> This vote is only for the purpose of unarchive and remove the
> deprecation
+1
Am Di., 18. Aug. 2020 um 06:59 Uhr schrieb Norman Breau <
nor...@normanbreau.com>:
> 1+
>
> Norman Breau
> Software Developer
>
> nor...@normanbreau.com (
>
+1
Am Di., 18. Aug. 2020 um 08:46 Uhr schrieb Dave Alden <
d...@workingedge.co.uk>:
> +1
>
> On Tue, 18 Aug 2020, 05:47 Bryan Ellis, wrote:
>
> > This vote is only for the purpose of unarchive and remove the deprecation
> > status for the plugin of:
> >
> > cordova-plugin-device-orientation
>
I think in the past we also got pushback from INFRA on using bots via
apps because of access to data etc (similar to CI services etc). Not
sure if that changed in the last few months.
J
Am Fr., 17. Apr. 2020 um 13:44 Uhr schrieb Niklas Merz :
>
> I think I have to agree there.
>
> I would vote
There are existing tools that do what you suggest Raphael, mostly to
put contributors into READMEs of projects but I am sure that could be
abused to put it into a Markdown file that is included in the docs.
Apache also has a site that lists all PMC members etc (that I think
uses some AJAX + a
This repository is misconfigured, these emails should probably go to the
commits mailing list and not dev. (Yep, the default in the infra tool is
not optimal here)
J
Am Fr., 8. Nov. 2019 um 21:05 Uhr schrieb GitBox :
> raphinesse opened a new pull request #10: feat: make base rules stricter &
>
ee now?
> Or should I create a new thread to discuss it again?
>
>
> El jue., 23 ago. 2018 a las 16:24, Jan Piotrowski ()
> escribió:
>
> > Here is the PR on GitHub templates, our usage of them and actual
> > drafts for all templates:
> > https://github.com/apache/cordova
Sounds great. Historically we always had trouble when Google decided
to replace/deprecate/change any of the tools in the build toolchain,
so keeping up to date what is the tool of the week sounds like a good
idea.
Important to consider is the availability of that tool for older
Android versions,
y wrote:
> >
> > I am now changing the "query" labels back to "question", though under
> > protest. I did already check that the new "info-needed" label is used
> > where it looked appropriate. But I don't see what documentation
> > change
+1 on #1, #2 and #3 - just don't forget to create the issue that makes
sure #3 will be taken care of later.
J
Am Di., 30. Juli 2019 um 14:10 Uhr schrieb Norman Breau
:
>
> Hello devs!
>
> I am writing to gather feedback on the new feature to support building
> the new android packaging format:
make this release this week?
>
> On Fri, Jul 5, 2019 at 9:50 AM Tim Brust
> wrote:
> >
> > For the lazy ppl, here is the diff:
> > https://github.com/apache/cordova-windows/compare/7.0.0...master
> > Go for it Jan! :)
> >
> > On Thu, Jul 4, 2019 at 5:5
. Juli 2019 um 08:20 Uhr schrieb Jan Piotrowski
:
>
> Chris, it has been over a week. What is the state of undoing the label
> and documentation changes?
>
> -J
>
> Am Mi., 17. Juli 2019 um 20:08 Uhr schrieb Jan Piotrowski
> :
> >
> > By renaming the label, you als
Chris, it has been over a week. What is the state of undoing the label
and documentation changes?
-J
Am Mi., 17. Juli 2019 um 20:08 Uhr schrieb Jan Piotrowski
:
>
> By renaming the label, you also renamed it for all existing issues.
> Now many labels that were just questions of users (
We had to roll back a misinformed change in
cordova-plugin-wkwebview-engine, so we have another bugfix release:
- cordova-plugin-wkwebview-engine@1.2.1
Am Do., 11. Juli 2019 um 18:02 Uhr schrieb Jan Piotrowski
:
>
> And finally the rest of the plugins:
>
> - cordova-plugi
The vote has now closed. The results are:
Positive Binding Votes: 3
* Jesse MacFadyen
* Bryan Ellis
* Jan Piotrowski
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
Am Mo., 22. Juli 2019 um 19:51 Uhr schrieb Jesse :
>
> +1
>
> - coho verfify-archive
>
Please review and vote on the release of this plugins release
by replying to this email (and keep discussion on the DISCUSS thread)
The plugins have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/cordova-plugin-wkwebview-engine-1.2.1/
The packages were published from
Does anyone have any reason to delay a cordova-plugin-wkwebview-engine release?
There is an ugly bug via one of the PRs that was merged that needs to be undone:
https://github.com/apache/cordova-plugin-wkwebview-engine/issues/105
https://github.com/apache/cordova-plugin-wkwebview-engine/pull/45
By renaming the label, you also renamed it for all existing issues.
Now many labels that were just questions of users (both open and
closed) indicate that info is needed - which might be true or not.
Please undo all renaming of labels, both to `info-needed` and `query`.
Please undo the changes to
Yeah, that was wrong.
- "question" classifies an issue into a category: bug, feature,
enhancement, support, discussion, question
- "info-needed" is just a tag similar to "invalid" or "has-pr"
Please stop rolling this out to other repositories.
Please revert the change to the "Default labels"
The nice thing about missing process is that one can do whatever one wants ;)
+1
Bonus points if you add it to
https://github.com/apache/cordova-contribute/blob/master/github-labels.md#custom-labels
and give it a nice vibrant color.
Am Mo., 15. Juli 2019 um 23:18 Uhr schrieb Darryl Pogue :
>
>
to those
and there are no massive problems, I will link to it here.
Am Di., 2. Juli 2019 um 20:24 Uhr schrieb Jan Piotrowski :
>
> We have just released an update to many of our plugins:
>
> - cordova-plugin-battery-status@2.0.3
> - cordova-plugin-device@2.0.3
> - cordova-pl
The vote has now closed. The results are:
Positive Binding Votes: 3
* Brian Ellis
* Tim Brust
* Jan Piotrowski
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
Am Do., 11. Juli 2019 um 08:54 Uhr schrieb Bryan Ellis :
>
> +1
>
> * Confirmed the sigs & hashes w
The vote has now closed. The results are:
Positive Binding Votes: 3
* Jesse MacFadyen
* Tim Brust
* Jan Piotrowski
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
Am Mo., 8. Juli 2019 um 09:15 Uhr schrieb Jesse :
>
> +1
>
> - CI is green
> - reviewed changes
Does anyone have any reason to delay a cordova-windows platform release?
Any outstanding patches to land?
If not, I will start the release soon.
(CI is currently red, so this will require some investigation.)
-
To unsubscribe,
We have just released an update to many of our plugins:
- cordova-plugin-battery-status@2.0.3
- cordova-plugin-device@2.0.3
- cordova-plugin-dialogs@2.0.2
- cordova-plugin-media-capture@3.0.3
- cordova-plugin-network-information@2.0.2
- cordova-plugin-screen-orientation@3.0.2
-
The vote has now closed. The results are:
Positive Binding Votes: 3
* Bryan Ellis
* Tim Brust
* Jan Piotrowski
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
Am Do., 27. Juni 2019 um 16:09 Uhr schrieb Tim Brust :
>
> I vote +1 *for each plugin*:
> * CI is green fo
The vote has now closed. The results are:
Positive Binding Votes: 3
* Bryan Ellis
* Tim Brust
* Jan Piotrowski
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
Am Do., 27. Juni 2019 um 15:42 Uhr schrieb Tim Brust :
>
> I vote +1:
> * CI is green for release tag
> *
The vote has now closed. The results are:
Positive Binding Votes: 3
* Bryan Ellis
* Tim Brust
* Jan Piotrowski
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
Am Do., 27. Juni 2019 um 15:47 Uhr schrieb Tim Brust :
>
> I vote +1:
> * CI is green for release tag
> *
The vote has now closed. The results are:
Positive Binding Votes: 3
* Bryan Ellis
* Tim Brust
* Jan Piotrowski
Negative Binding Votes: 0
The vote has passed.
Thanks everyone!
Am So., 23. Juni 2019 um 10:28 Uhr schrieb Bryan Ellis :
>
> +1
>
> * Confirmed sigs & hashes w
Small correction:
The package on dist/dev for inappbrowser was published from this
corresponding git tag:
cordova-plugin-inappbrowser: 3.1.0 (1cb4be15b8)
-J
Am Fr., 28. Juni 2019 um 14:50 Uhr schrieb Jan Piotrowski
:
>
> Please review and vote on the release of these plugins re
+1
- CI is green
- Changes make sense
- I could successfully build an app with it
Am Fr., 28. Juni 2019 um 15:25 Uhr schrieb Tim Brust :
>
> I vote +1:
> * CI is green for release tag
> * coho verify-archive ✅
> * coho check-license ✅
> * npm audit ✅
> * npm test ✅
>
> On Fri, Jun 28, 2019 at
Please review and vote on the release of these plugins releases
by replying to this email (and keep discussion on the DISCUSS thread)
The plugins have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/cordova-plugin-file-6.0.2/
Please review and vote on the release of these plugins releases
by replying to this email (and keep discussion on the DISCUSS thread)
Two of these minor updates are comparably big, see their release notes:
https://github.com/apache/cordova-plugin-camera/blob/master/RELEASENOTES.md#410-jun-27-2019
Note that the dist/dev link shows the correct link, but links to a wrong URL.
This is the correct one:
https://dist.apache.org/repos/dist/dev/cordova/cordova-plugin-device-2.0.3/
-J
Am Sa., 15. Juni 2019 um 00:40 Uhr schrieb Jan Piotrowski
:
>
> Please review and vote on the r
Please review and vote on the release of these plugins releases
by replying to this email (and keep discussion on the DISCUSS thread)
The plugins have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/cordova-plugin-dialogs-2.0.2/
Please review and vote on the release of this plugins release
by replying to this email (and keep discussion on the DISCUSS thread)
The plugins have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/cordova-plugin-device-2.0.3/
+1
Changes since 3.1.0 look good.
(Waiting for CI to turn green on release commit though.)
Am Mi., 12. Juni 2019 um 10:59 Uhr schrieb Chris Brody <
chris.br...@gmail.com>:
> Please review and vote on this cordova-common@3.2.0 tools release by
> replying to this email (and keep discussion on
Hi all,
in the last few days I spent quite a lot of time trying to write an
abstracted release process documentation for all our different
components (as a base for some automation). During that, I discovered
that we actually have 2 very different release processes.
It boils down to these two
Thu, May 16, 2019 at 2:16 PM Jan Piotrowski wrote:
>
> > None of the plugins have a `hooks` directory or anything else that
> > looks similar.
> >
> > Is anyone aware of any script in the plugin repositories that is
> > executed on the developer side?
> >
019 um 10:03 Uhr schrieb Jan Piotrowski <
> piotrow...@gmail.com>:
>
> > Currently our plugin CI uses the same version of Node.js as Tooling
> > and Platforms, until recently 4.2 and now 6.
> >
> > But if I am not mistaken, our plugins do not contain any scripts tha
While rewriting the plugin release documentation, I stumbled over the
way coho chooses the directory where it does its changes. As this is
probably just because of historical reasons, I suggest we change the
way it works:
https://github.com/apache/cordova-coho/issues/238
Is there any reason to
Please review and vote on the release of this plugins release
by replying to this email (and keep discussion on the DISCUSS thread)
The plugins have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/cordova-plugin-vibration%2381/
The packages were published from their
I would say "No" to 1) and 3) - we can get rid of the code and
deactivate that account.
2) and 4) definitely need their own mailing list thread with their own
reasoning.
-J
Am Do., 16. Mai 2019 um 07:19 Uhr schrieb Dmitry Blotsky
:
>
> Ok, if that’s reality, then it’s reality. Then, if we’re on
Currently our plugin CI uses the same version of Node.js as Tooling
and Platforms, until recently 4.2 and now 6.
But if I am not mistaken, our plugins do not contain any scripts that
are executed on the developer machine, only JavaScript files that are
run inside the app or native code. So it
te and fix - or remove the CI
builds where appropriate (e.g. testing on browsers where the Browser
platform is not even supported).
I am still quite happy with the success rate, 9 success vs. 6 fail is
better than I expected.
Best,
Jan
Am Mi., 24. Apr. 2019 um 17:27 Uhr schrieb Jan Piotrowski
:
>
While that is correct, nvm-windows indeed had problems with npx not
working after it was first added to node - so Julio's was indeed true
in the past.
Luckily it was fixed, so even we lowly Windows users now can use npx.
Am Fr., 10. Mai 2019 um 09:48 Uhr schrieb Oliver Salzburg
:
>
> npx ships
Afaik nvm-windows also supports npx for quite some time [1], with
1.1.7 it works for every new-ish node I installed.
[1]
https://github.com/coreybutler/nvm-windows/commit/ce756027a816042ed41c3ee60b18d0ebc2599c2b
Am Fr., 10. Mai 2019 um 02:09 Uhr schrieb julio cesar sanchez
:
>
> npx is included
many plugins
at the same time again, so this is not a solution.
Ideas?
Best,
Jan
Am Mi., 8. Mai 2019 um 20:11 Uhr schrieb Jan Piotrowski :
>
> This is now being tracked in https://github.com/apache/cordova/issues/104
>
> Am Mo., 6. Mai 2019 um 12:19 Uhr schrieb Jan Piotrowski
> :
> &
Please review and vote on the release of this plugins release
by replying to this email (and keep discussion on the DISCUSS thread)
The plugins have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/splash20190509/
The packages were published from their corresponding git
This is now being tracked in https://github.com/apache/cordova/issues/104
Am Mo., 6. Mai 2019 um 12:19 Uhr schrieb Jan Piotrowski :
>
> Does anyone have any reasons to delay Cordova Plugins releases?
> If not, I will start the releases tomorrow.
>
>
> Cordova Paramedic is s
Does anyone have any reasons to delay Cordova Plugins releases?
If not, I will start the releases tomorrow.
Cordova Paramedic is soon [1] in a state where we can start rolling
out its CI configuration to our plugin repositories. This will enable
us to evaluate the state of a plugin repository
Imagine I want to create a new Cordova platform.
What documentation should I read?
Which repositories can help me?
I see https://github.com/apache/cordova-test-platform exists, but is this
complete and current?
What functionality should I implement first?
Is there a way to "fake" a platform
Which is all nice and interesting but absolutely unrelated to this thread's
topic and my initial question.
Please stop moving threads offtopic and create your own mailing list thread
if you want to talk about something.
Thanks.
Am Do., 2. Mai 2019 um 00:31 Uhr schrieb Chris Brody :
> > Is it
rything from the cordova.js and the bridge would have to change, and
> every plugin would need to be rewritten.
>
> Cheers,
> Jesse
>
> @purplecabbage
> risingj.com
>
>
> On Wed, May 1, 2019 at 1:03 PM Jan Piotrowski wrote:
>
> > For Cordova iOS and Cordova
For Cordova iOS and Cordova Android it is possible to create plugins
that create native UI on top of your app - you just include the
libraries in your plugin and execute their API. Example for Android
InAppBrowser:
. Apr. 2019 um 14:08 Uhr schrieb Jan Piotrowski
:
>
> Hi,
>
> in the last few days I have been working on fixing and updating the CI
> configuration of our plugins, so they actually work with Cordova CLI 9
> and are tested on all relevant OS versions via SauceLabs.
>
> You mi
+1
* CI is green
* Diff makes sense
* release branch looks right
Am Fr., 19. Apr. 2019 um 02:53 Uhr schrieb Bryan Ellis :
>
> +1
>
> * Verified archive signatures & hashes with `coho verify-archive`
> * Verified tags SHA with `coho verify-tags`
> * Re-created npm package to validate matching
Hi,
in the last few days I have been working on fixing and updating the CI
configuration of our plugins, so they actually work with Cordova CLI 9
and are tested on all relevant OS versions via SauceLabs.
You might know that our plugin tests are run via cordova-paramedic,
which means that the CI
ut yes, as Jan said, we only need to merge and it will be released.
>
> On Mon, Mar 18, 2019 at 6:22 PM Jan Piotrowski wrote:
>
> > As Julio noticed, there is no release process for docs - what is
> > merged is deployed.
> >
> > But yes, Cordova Android is missing
As Julio noticed, there is no release process for docs - what is
merged is deployed.
But yes, Cordova Android is missing the new API levels and probably
some documentation on the new features.
-J
Am Mo., 18. März 2019 um 09:43 Uhr schrieb julio cesar sanchez
:
>
> I don’t think the docs follow
The PR is marked as Work in Progress. If you want it to get reviewed
and merged you should remove that.
Am Fr., 15. März 2019 um 13:18 Uhr schrieb Oliver Salzburg
:
>
> I really think we should get #680[1] merged before the release.
>
> It should be good in a moment.
>
> [1]:
+1
- CI is green
- changes make sense
Am Di., 5. März 2019 um 10:33 Uhr schrieb Jesse :
>
> +1
>
> - Ran coho verify-archive
> - CI was green
>
>
> @purplecabbage
> risingj.com
>
>
> On Mon, Mar 4, 2019 at 11:54 PM Bryan Ellis wrote:
>
> > Please review and vote on this Windows Release v7.0.0
>
+1
* CI is green
* changes make sense
Am Di., 5. März 2019 um 07:14 Uhr schrieb Ken Naito :
>
> +1
>
> * coho verify-archive OK
> * coho verify-tags OK (except for confirming signature owner)
> * The last commit 8649e607d605f8c705b983d7042aa73ba7da1c4f passes CI tests.
>
>
> Note that I added
>
+1
RELEASENOTES.md is missing the 7.1.x releases because they weren't merged
back from the release branch, but that does not block the release and can
just be fixed on master now.
- installed the platform with current CLI and added a few plugins
- build and ran an app on an Nexus 5
- CI is
. 2019 um 12:30 Uhr schrieb julio cesar sanchez
:
>
> 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 Piotro
be managed by the user
> > > > > somehow?
> > > > >
> > > > > El vie., 18 ene. 2019 a las 15:02, Chris Brody
> > > > > ()
> > > > > escribió:
> > > > >
> > > > > > I am investigating a quick s
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
Hey Martina,
what areas are you most interested in? Code or documentation?
What is your experience with JS software, besides writing Cordova apps?
If you are looking for a way to contribute with comparatively little setup:
We have a big backlog of Pull Requests for core plugins. Those usually
Any reason you skipped this documented release step?
https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#android-only-uploading-to-bintray
> Also can someone explain the use case for publishing on Maven?
Cordova Android is made available via Bintray/Maven so it
> I think we should agree before any issue is created.
>
> > El lun., 10 dic. 2018 a las 17:54, Chris Brody ()
> > escribió:
>
> > And you can find Cordova email archive in:
> > https://lists.apache.org/list.html?dev@cordova.apache.org
> > On Mon, Dec 10, 20
think this should be possible with preference tags in the config.xml, we
> > should be able to read them and set those values to true or false, being
> > the default the current one so it's not a breaking change.
>
> > El jue., 6 dic. 2018 a las 16:45, Jan Piotrowski (
Hi.
For several open tasks (e.g. updating `package.json` across many
repos, distributing the GitHub Issue and PR templates, updating the
plugin CI configuration) we will have to change files in many
repositories and then create a PR (which means the changes have to be
applied in a new branch or
+1
Thanks to you both!
Am Fr., 7. Dez. 2018 um 10:05 Uhr schrieb julio cesar sanchez
:
>
> +1
>
> And thanks to you for all this years and to him for taking over
>
> El El vie, 7 dic 2018 a las 8:02, Toplak Daniel
> escribió:
>
> > Hello Shazron,
> >
> > thank you for your hard work the last few
> I read through the other threads. [...]
Please reply to questions from other threads in these threads instead
of interlinking two discussions that are about related, but different
things. Thanks.
-J
Am Do., 6. Dez. 2018 um 16:16 Uhr schrieb Chris Brody :
>
> > After a few questions about
What other use cases besides `setAllowFileAccess` do you see here?
-J
Am Do., 6. Dez. 2018 um 14:36 Uhr schrieb MALEYRIE Stephane (AIM
Services) :
>
> Hello,
>
> After a few questions about changing an attribute of the WebSettings of the
> WebView (setAllowFileAccess) here :
>
Aside:
By definition WIP (Work in Progress) pull requests should not be
reviewed. If someone ignores that, I think it is fair to dismiss all
the reviews without further comment.
-J
Am Di., 4. Dez. 2018 um 19:16 Uhr schrieb Chris Brody :
>
> By "user-defined Gradle files" I meant what someone can
um 17:51 Uhr schrieb Jan Piotrowski
:
>
> I just finished revising my PRs regarding the deprecation and
> archiving of repositories. Finishing this is needed to actually be
> able to go ahead and vote on the archival of the first repositories.
>
> 1. First one is a general "De
Hi Stéphane,
there is a newer version of cordova-android available: 7.x.x -
currently 7.1.4. That means that we, the volunteer development team,
won't do any more updates to the 6.x branch. So even if we implement
any new features here, they will only get released for 7.x.
Any particular reason
Another PR that I polished a bit and is ready for feedback and
reviews: "Create a Minimal Reproduction Repository or Sample"
PR: https://github.com/apache/cordova-contribute/pull/6
Preview:
I just finished revising my PRs regarding the deprecation and
archiving of repositories. Finishing this is needed to actually be
able to go ahead and vote on the archival of the first repositories.
1. First one is a general "Deprecation and Archiving Policy" that
would be available on our website
It is important to note here to the casual observer, that of course
not _all_ configuration will be moved to package.json - only the stuff
that fits there better.
Darryl explained that above, this is mainly about moving the
"dependency" definitions right now - the rest will stay unchanged.
-J
Am
Even more context:
https://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html
Am Di., 27. Nov. 2018 um 23:21 Uhr schrieb Jan Piotrowski
:
>
> You probably refer to the "Cordova Plugin Registry":
>
> * https://cordova.apache.org/news/2013/10/21
You probably refer to the "Cordova Plugin Registry":
* https://cordova.apache.org/news/2013/10/21/cordova-registry.html
✞ https://cordova.apache.org/news/2015/09/08/cpr-readonly.html
-J
Am Di., 27. Nov. 2018 um 23:17 Uhr schrieb Darryl Pogue :
>
> plugreg was a 3rd party website displaying
n then merge them. Thanks.
-J
Am Sa., 24. Nov. 2018 um 12:29 Uhr schrieb Jan Piotrowski
:
>
> After spending some time with it, I think I have a rough idea:
>
> `Mobile Spec` has 3 parts:
>
> 1. The main folder is a Cordova app "template" (`config.xml` and
> `www
I learned and will create several PRs that I will announce here
when done.
-J
Am Fr., 23. Nov. 2018 um 19:37 Uhr schrieb Jan Piotrowski
:
>
> Some historical context:
> https://phonegap.com/blog/2009/11/04/mobile-spec-is-here/
> (original at
> http://web.archive.org/web/2012042817191
in https://github.com/apache/cordova/issues/54
> > On Fri, Nov 23, 2018 at 6:33 AM Jan Piotrowski
> > wrote:
> > >
> > > Great, please also update mobilespec documentation on how to use this
> > > - that really needs some refreshing.
> > > Am Fr.,
://www.feedhenry.com/extending-cordova-mobile-spec-tester-app-cloud/
Am Fr., 23. Nov. 2018 um 19:20 Uhr schrieb Jan Piotrowski
:
>
> Hey Cordova veterans,
>
> We are currently looking into improving the platform testing, release
> and voting process (to avoid issues like the broken plugi
Hey Cordova veterans,
We are currently looking into improving the platform testing, release
and voting process (to avoid issues like the broken plugins in
cordova-android 7.1.3) in https://github.com/apache/cordova/issues/54
There we stumbled over mobile-spec as another form of testing the app.
+1 for both
* Created and started hello world app
* Confirmed hello world app also starts with
`cordova-plugin-inappbrowser` and `cordova-plugin-local-notification`
installed
* Windows/AppVeyor CI is red for the tagged commit (because of
AppVeyor infrastructure things, see
chance. I was able to get
> most of the "automatic" mobilespec tests to succeed, but selecting 1
> plugin at a time to run the tests on. I will go ahead with the patch
> release now.
> On Thu, Nov 22, 2018 at 5:37 PM Jan Piotrowski wrote:
> >
> > I created https://githu
> El El jue, 22 nov 2018 a las 23:12, Jan Piotrowski
> escribió:
>
> > No reason to slow down the release process - anyone can do that for
> > themselves and -1 the release vote if it shows a problem.
> > Am Do., 22. Nov. 2018 um 20:55 Uhr schrieb Chris Brody <
> >
No reason to slow down the release process - anyone can do that for
themselves and -1 the release vote if it shows a problem.
Am Do., 22. Nov. 2018 um 20:55 Uhr schrieb Chris Brody :
>
> I can look into that tomorrow. It would definitely delay the release,
> unless someone else wants to pick this
#555 links to PRs and issues randomly - I have no idea what is going on there.
Please update the PR description to link to the Pull Requests whose
changes are included in this PR (and optionally the issue those are
solving).
-J
Am Do., 15. Nov. 2018 um 14:00 Uhr schrieb Chris Brody :
>
> Changes
eaking changes in platform but just curious to resolve this issue as
> we may encounter this error anytime in future.
>
> Let me know your thoughts.
>
> On Wed, Oct 31, 2018 at 11:07 PM Jan Piotrowski
> wrote:
>
> > Gandhi, what exactly did you do until now? Do you have
Gandhi, what exactly did you do until now? Do you have a checkout of
all the Cordova repos created with coho?
Please reply with the exact command you are running and error/output
you are getting.
J
Am Sa., 27. Okt. 2018 um 11:02 Uhr schrieb gandhi rajan
:
>
> Hi Raphinesse, Thanks for the
Julio, I would be happy to pair with you on some plugin releases.
As you already noticed, the release processes via coho need some
serious work now that we are on GitHub issues instead of JIRA, so we
have some additional work ahead of us.
First step would be to identify which plugin to start
I vote +1:
- Ran `coho verify-tags -g` with the tag string from above
- Confirmed sigs & hashes with `coho verify-archive`
- Checked that the changes in the 8.1.x branch should do what the
"release issue" and changelog says
- Checked out 8.1.x branch and successfully ran `npm t` (and observed
1
Hi interested people.
I spent the last few days unblocking pull requests for our plugin
repositories. This meant fixing our test configuration, fixing some
specific problems of our test infrastructure and in general making
sure that PRs with failing tests were fixed and rerun.
The result: 83
1 - 100 of 237 matches
Mail list logo
