using @latest isn't necessary as that is the default. We have never had
@latest be part of our install instructions before, why add more characters?
Updated the rest.
https://github.com/cordova/apache-blog-posts/blob/master/2015-09-09-tools-release.md
Posting soon.
On Tue, Sep 8, 2015 at 8:13
https://github.com/cordova/apache-blog-posts/blob/master/2015-09-08-tools-release.md
Leave comments and feedback here.
Use @latest for install instructions cordova@latest plugman@latest
blackberry10@3.8.0 is already released
Pinned blackery10@~3.8.0 browser@~4.0.0 windows@~4.1.0
caret(^)
On Tuesday, September 8, 2015, Steven Gill wrote:
>
>
You might want to add a PS: cpr immutable, expect to shutdown Oct 15th, NPM
registry FTW, We hide @ slack.cordova.io
On Tuesday, September 8, 2015, Carlos Santana wrote:
> Use @latest for install instructions cordova@latest plugman@latest
>
> blackberry10@3.8.0 is already
Please review. https://github.com/cordova/apache-blog-posts/pull/43
I added a comment to the PR (nit + questions about pinned versions).
Otherwise LGTM.
On 8/13/15, 2:11 AM, Steven Gill stevengil...@gmail.com wrote:
Please review. https://github.com/cordova/apache-blog-posts/pull/43
-
To
Please send pull requests for any fixes.
https://github.com/cordova/apache-blog-posts/blob/master/2015-06-10-tools-release.md
I will be publishing this tomorrow.
Having trouble building the site. Seems to happen every few months. Blog
post is ready but the CSS is not properly generating for me.
On Fri, Feb 27, 2015 at 6:47 PM, Gorkem Ercan gorkem.er...@gmail.com
wrote:
On 27 Feb 2015, at 21:16, Michal Mocny wrote:
Looks good. Few comments:
- You
Looks good. Few comments:
- You can manage plugin and platform versions using the --save command =
You can now save your list of installed plugins and platforms using the
--save command.
- (I don't think --save actually helps with management of versions)
- We are going to be doing a blog post
On 27 Feb 2015, at 21:16, Michal Mocny wrote:
Looks good. Few comments:
- You can manage plugin and platform versions using the --save
command =
You can now save your list of installed plugins and platforms using
the
--save command.
Should we also add Saved platforms and plugins are
Still have some formatting to do of the changes.
https://github.com/cordova/apache-blog-posts/blob/master/2015-03-02-tools-release.md
Any other highlights I should mention?
On Mon, Jan 12, 2015 at 6:57 PM, Steven Gill stevengil...@gmail.com wrote:
I see your point.
We have chatted about moving platform specific JS into the platform repos
for a while. I agree that is something we should do now.
On Sat, Jan 10, 2015 at 5:27 PM, Andrew Grieve
I see your point.
We have chatted about moving platform specific JS into the platform repos
for a while. I agree that is something we should do now.
On Sat, Jan 10, 2015 at 5:27 PM, Andrew Grieve agri...@chromium.org wrote:
An example is android-3.7.0 adding an extra prompt() on start-up
An example is android-3.7.0 adding an extra prompt() on start-up that
retrieves a nonce from the native side. If any pre-3.7.0 were to use this
newer JS, it would likely show a prompt() on start-up.
The app plugin is not a real plugin only because we want it installed be
default.
I think the
Steven Gill wrote:
https://github.com/cordova/apache-blog-posts/blob/master/2015-01-08-tools-
release.md
PRs welcome!
https://github.com/cordova/apache-blog-posts/pull/28
smime.p7s
Description: S/MIME cryptographic signature
Thanks for PRs.
Andrew, the browserify method builds a cordova-js for each of the installed
platforms (at prepare time) and copies it over into the platforms www
directory (platforms/android/assets/www, etc). We shouldn't have to move
platform specific js into platform folders because it is still
On Fri, Jan 9, 2015 at 2:26 PM, Steven Gill stevengil...@gmail.com wrote:
Thanks for PRs.
Andrew, the browserify method builds a cordova-js for each of the installed
platforms (at prepare time) and copies it over into the platforms www
directory (platforms/android/assets/www, etc). We
What are some examples of older platforms that can't use the newer exec
code? I don't think this is a usecase that is very common (using fairly
outdated platforms with new cli). Maybe a solution would be that newer
versions of the cli don't work with those old versions of platforms.
In terms of
https://github.com/cordova/apache-blog-posts/blob/master/2015-01-08-tools-release.md
PRs welcome!
Are there any changes at all to plugman that necessitate its release, or is
it just being released so that there's a version that uses the new
cordova-lib? It seems odd that it's in the announcement, but missing from
the releasenotes.
On Fri Nov 07 2014 at 5:22:51 PM Mark Koudritsky
It's for the lib, other changes are mostly fixes in help text.
Should I add some trivial line about plugman to release notes?
On Mon, Nov 10, 2014 at 9:17 AM, Ian Clelland iclell...@chromium.org
wrote:
Are there any changes at all to plugman that necessitate its release, or is
it just being
You mention near the top that the iOS, Windows, and WP8 platforms are updated,
but there isn't mention of what that is. One could infer that this release has
those updates, but I realize it's just changing the default versions of those
platforms on an add. How about linking to those posts:
The two items under Platform updates are already links to those two posts.
On Mon, Nov 10, 2014 at 10:56 AM, Marcel Kinard cmarc...@gmail.com wrote:
You mention near the top that the iOS, Windows, and WP8 platforms are
updated, but there isn't mention of what that is. One could infer that this
Ah, missed that.
On Nov 10, 2014, at 11:20 AM, Mark Koudritsky kam...@google.com wrote:
The two items under Platform updates are already links to those two posts.
On Mon, Nov 10, 2014 at 10:56 AM, Marcel Kinard cmarc...@gmail.com wrote:
You mention near the top that the iOS, Windows, and
To be fair, if you missed it, others will too, which argues that it should
be reorganized.
I've done a PR for the other bits, but someone should consider this point.
On 11/10/14, 11:27 AM, Marcel Kinard cmarc...@gmail.com wrote:
Ah, missed that.
On Nov 10, 2014, at 11:20 AM, Mark Koudritsky
I only did the PR there because that's what I saw advertised.
I don't really care where it is done :)
On 11/10/14, 1:00 PM, Marcel Kinard cmarc...@gmail.com wrote:
https://github.com/kamrik/apache-blog-posts/pull/2
BTW, is there a reason to do the work on kamrik/master instead of
This was a huge security hole fix that should be mentioned most likely.
https://github.com/apache/cordova-lib/commit/281aee737dbe5143c9cb5957359ed5df6298a154
This landed quietly, but ultimately tooling released before this commit could
read private user data, copy it to the project folder and
Mark, I added you as owner to that Org.
-Steve
On Mon, Nov 10, 2014 at 11:30 AM, Mark Koudritsky kam...@google.com wrote:
I got a permission denied error when trying to push to origin. Didn't
invest the time to investigate it. Does this repo live on GitHub or is it
only mirrored there?
I'm assuming I can't push there either...
On 11/10/14, 2:41 PM, Steven Gill stevengil...@gmail.com wrote:
Mark, I added you as owner to that Org.
-Steve
On Mon, Nov 10, 2014 at 11:30 AM, Mark Koudritsky kam...@google.com
wrote:
I got a permission denied error when trying to push to origin.
Added some lines: https://github.com/cordova/apache-blog-posts/pull/20
On Mon, Nov 10, 2014 at 1:23 PM, Mark Koudritsky kam...@google.com wrote:
Incorporated pull request from Josh and Marcel, added the CB-7890 to
notable changes in the lib, bumped micro numbers for versions that will
have to
Please review and send PRs!
https://github.com/kamrik/apache-blog-posts/blob/master/2014-11-10-tools-release.md
31 matches
Mail list logo