Seems like we are good to go for this plugin. I will start the release now!
Am 02.06.20 um 20:39 schrieb Niklas Merz:
> Hi all,
>
> Since cordova-ios 6.0, which includes a splashscreen implementation, was
> released recently, we should release a patch version of the splashscreen
> plugin which
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-splaschreen-5.0.4/
The packages were published from their
(sending again because previous email was attached to discuss thread)
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/cor
Hey folks,
The File Transfer plugin has been officially deprecated since 2017:
https://cordova.apache.org/blog/2017/10/18/from-filetransfer-to-xhr2.html
However, the repo and npm have no link to that page or any sort of
indication that it is not maintained.
With the release of cordova-ios 6, the
Correction: There is in fact a deprecation notice, part-way down the
README, but it's not especially attention grabbing and I missed it the
first 2 times I skimmed the file.
On Wed, Jun 3, 2020 at 11:55 AM Darryl Pogue wrote:
> Hey folks,
>
> The File Transfer plugin has been officially deprecat
I'm sure you're not the only one who misses it, considering the repo is
still pretty active in terms of new issues being reported.
On 2020-06-03 3:59 p.m., Darryl Pogue wrote:
Correction: There is in fact a deprecation notice, part-way down the
README, but it's not especially attention grabbing
+1 The deprecation notice needs to be prominent, I missed it myself on a
quick scroll.
Some of that readme is in a specific format to support appearance in
docs.cordova.io ( similar to
https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-file/index.html
)
This is no longer a requirem
This happens with all the deprecated plugins we have, people keeps
reporting issues on them.
I proposed long ago to archive them, but some people was against it, but I
think archiving is the way to go when something is deprecated.
El miércoles, 3 de junio de 2020, Jesse escribió:
> +1 The depre
+1 on archiving/adding [DEPRECATED] text in the description.
On 2020-06-03 4:25 p.m., julio cesar sanchez wrote:
This happens with all the deprecated plugins we have, people keeps
reporting issues on them.
I proposed long ago to archive them, but some people was against it, but I
think archivin
While I agree that we should somehow archive old code, I'm still -1 on a
deprecation of this plugin. (We've had some discussion about it here, too:
https://github.com/apache/cordova/issues/185)
XHR is not reliable and causes OOM errors when handling large data.
On Wed, Jun 3, 2020 at 7:29 PM Nor
Not that we want to outright endorse 3rd party plugins without due
diligence, but there are other options than the FileTransfer plugin, such
as https://www.npmjs.com/package/cordova-plugin-advanced-http
On Wed, Jun 3, 2020 at 1:46 PM Tim Brust wrote:
> While I agree that we should somehow archiv
I think people knew they were leaving the project and voted to deprecate
plugins to leave less things to maintain to the few remaining people.
Since there are new committers now that didn’t vote, maybe we can
reconsider/re vote.
El miércoles, 3 de junio de 2020, Darryl Pogue
escribió:
> Not t
We probably should resolve the travis issue, just to be sure it isn't
hiding some other error.
ld: warning: ignoring file /tmp/libCordova.a, file was built for archive
which is not the architecture being linked (i386): /tmp/libCordova.a
658Undefined symbols for architecture i386:
659"_OBJC_CLA
I must say I don't really understand that failure, too. I think it's something
strange in the CI/Travis. (Hopefully this will be on Github Actions, too
sometime). CI uses Xcode 10.3 which is not supported by our latests cordova-ios
anymore.
I think we should not rely on the CI tests for this qu
14 matches
Mail list logo
