@brody4hire - C. Jonathan Brody
@brody4hire - C. Jonathan Brody
I think this is not clear for all members.
The documented procedure is to use JIRA issues when publishing tools, platforms, or plugins releases. Now that GitHub issues are enabled ~~I would much rather track release items there~~ _and...
In case of a failed release vote the procedure for tools is to continue with the next release tag while the procedure for plugins and platforms is to reuse the...
### Platforms affected All ### What does this PR do? Add section with note to ensure that changes are made in a "-dev" version. This is a partial workaround for...
While trying to help someone else I find the concept of "tools release" as discussed in https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md to be a bit confusing. I would be a bit happier to see...
- Same cordova-js build for all platforms. Use of concepts such as IOC (inversion of control), DI, factory functions, etc. to keep same common JavaScript for all platforms, with limited...
The requirement to wait for the `deviceready` event has caused some major confusion and other trouble for people using Ionic 2 and other Angular derivatives with the sqlite plugin. Here...
part of migration from JIRA (#75), cleanup of old JIRA issues (#93)?
If I do `cordova create` to generate a project the generated `www` code includes Apache copyright/license statement. I would rather see the template code under CC0 or public domain license,...
I discovered which looks like a really nice way to deal with minor patches needed. I have no idea if there is any way people can use this to patch...