Re: [VOTE] Tools Release, take 3

[Mark Koudritsky]

Ok, just published it all. Thanks for help and support.

Another question, for blog post the instructions look as follows:
cd cordova-website
rake build
svn st
svn add blah.blah.blah
svn commit -m "$JIRA Published blog post for tools release."

The `svn st` shows a bunch of stuff I had no intention to change. The
changes are subtle, mostly line breaks that don't show in rendered HTML
anyway. Solved it this time by running rake build with and without the new
post, diffing the entire site dir and only commiting the files that
changed. But this is rather laborious and fragile. Did I miss something
with setting up rake properly?

Re: [VOTE] Tools Release, take 3

[Josh Soref]

Mark Koudritsky wrote:
>Thanks for testing everyone, sending out an official results email
>soon. Josh thanks for the fixes in blog post. I've merged them in.


> The blog
>post pull request also contains a change
>1357dbe1770db735d15bf79986>
>to the win certificate post which I didn't merge. Windows people, please
>take a look at it.

I considered making that a distinct pull request, but since it was
referenced by the other blog thing, it made some sense to me to include it
— I regret this

>Anyone knows why the pull request still shows commits that are already
>merged in? I had the impression that GitHub pull request should be the
>same
>as
>git log master..jsoref/2014-11-10-tools-release
>which only shows one commit that is not yet merged

Apparently github is just "special"

"github does not look for partial merges"
"it's a downside of the caching strategy"

—

I was given advice about a possible workaround to get things to somewhere
useful.

Re: [VOTE] Tools Release, take 3

[Mark Koudritsky]

The vote has now closed. The results are:

Positive Binding Votes: 3
 - Parashuram Narasimhan
 - Sergey Grebnov
 - Mark Koudritsky

Negative Binding Votes: 0


The vote has passed.


On Thu, Nov 13, 2014 at 3:06 PM, Mark Koudritsky  wrote:

> Thanks for testing everyone, sending out an official results email
> soon. Josh thanks for the fixes in blog post. I've merged them in. The blog
> post pull request also contains a change
> 
> to the win certificate post which I didn't merge. Windows people, please
> take a look at it.
>
> Anyone knows why the pull request still shows commits that are already
> merged in? I had the impression that GitHub pull request should be the same
> as
> git log master..jsoref/2014-11-10-tools-release
> which only shows one commit that is not yet merged
>
> On Thu, Nov 13, 2014 at 12:09 PM, Josh Soref 
> wrote:
>
>> Ray Camden wrote:
>>
>> > +1 to this.
>>
>> > That was my first though - a ‘regular’ user may be confused
>> > and think they need to get this when they don’t.
>>
>> https://github.com/cordova/apache-blog-posts/pull/22 has a change that
>> should address it
>>
>> You can view it here:
>>
>> https://github.com/jsoref/cordova-apache-blog-posts/blob/ac170a3d6927dbede0
>> a297a5bf567b847d73100c/2014-11-10-tools-release.md
>> 
>>
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>
>

Re: [VOTE] Tools Release, take 3

[Mark Koudritsky]

Thanks for testing everyone, sending out an official results email
soon. Josh thanks for the fixes in blog post. I've merged them in. The blog
post pull request also contains a change

to the win certificate post which I didn't merge. Windows people, please
take a look at it.

Anyone knows why the pull request still shows commits that are already
merged in? I had the impression that GitHub pull request should be the same
as
git log master..jsoref/2014-11-10-tools-release
which only shows one commit that is not yet merged

On Thu, Nov 13, 2014 at 12:09 PM, Josh Soref  wrote:

> Ray Camden wrote:
>
> > +1 to this.
>
> > That was my first though - a ‘regular’ user may be confused
> > and think they need to get this when they don’t.
>
> https://github.com/cordova/apache-blog-posts/pull/22 has a change that
> should address it
>
> You can view it here:
> https://github.com/jsoref/cordova-apache-blog-posts/blob/ac170a3d6927dbede0
> a297a5bf567b847d73100c/2014-11-10-tools-release.md
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

Re: [VOTE] Tools Release, take 3

[Josh Soref]

Ray Camden wrote:

> +1 to this.

> That was my first though - a ‘regular’ user may be confused
> and think they need to get this when they don’t.

https://github.com/cordova/apache-blog-posts/pull/22 has a change that
should address it

You can view it here:
https://github.com/jsoref/cordova-apache-blog-posts/blob/ac170a3d6927dbede0
a297a5bf567b847d73100c/2014-11-10-tools-release.md





-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

RE: [VOTE] Tools Release, take 3

[Sergey Grebnov (Akvelon)]

I vote +1
•   Installed from archives, tested core platforms can be added, built and 
run

Thx!
Sergey
-Original Message-
From: Parashuram Narasimhan (MS OPEN TECH) [mailto:panar...@microsoft.com] 
Sent: Thursday, November 13, 2014 8:32 AM
To: dev@cordova.apache.org
Subject: RE: [VOTE] Tools Release, take 3

Voting +1

•   Verified signatures and hashes via ‘coho verify-archive’. Pass
•   Manually verified tags. Pass
•   Installed Cordova from archives. Pass 
•   Installed/uninstalled Cordova with npm via ‘npm install cordova@rc’. 
Pass
•   Verified ability to update Cordova from older version Pass
•   Verified ability to create Cordova app with windows and wp8 platforms 
(--usenpm / --usegit flags)
•   Built app for different archs (x86, x64, arm, anycpu). Pass
•   Ran app with target keys and vers

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Thursday, November 13, 2014 7:25 AM
To: dev@cordova.apache.org
Subject: Re: [VOTE] Tools Release, take 3

Ray Camden wrote:
> To update your tools:
>
> npm install -g cordova
> npm install -g plugman
>
> To be clear, a "regular" user doesn't need to update plugman, right?

I think there is a workflow where a regular user uses `plugman` directly (I 
think it's probably one where you aren't using cordova, but instead use 
cordova-{platform}/bin/create and friends).

Otherwise, if you only use `cordova` directly, then the plugman it uses would 
be updated automatically by updating cordova, and you'd be fine.

Afaiu, there are three workflows:
1. Plugin author — uses plugman directly 2. Single-platform writer — 
potentially uses plugman directly 3. Multiplatform writer — uses cordova (and 
everything else is used
indirectly)

The instructions would probably benefit from "if you have foo installed, use X 
to update it".

B CB  [  
X  ܚX KK[XZ[  ] ][  X  ܚX P ܙݘK \X K ܙ B  ܈Y][ۘ[  [X[  K[XZ[  
] Z[ ܙݘK \X K ܙ B B 
CB  [  X  
ܚX KK[XZ[
 ] ][  X  ܚX P ܙݘK \X K ܙ B  ܈Y][ۘ[  [X[  K[XZ[
 ] Z[ ܙݘK \X K ܙ B

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

RE: [VOTE] Tools Release, take 3

[Parashuram Narasimhan (MS OPEN TECH)]

Voting +1

•   Verified signatures and hashes via ‘coho verify-archive’. Pass
•   Manually verified tags. Pass
•   Installed Cordova from archives. Pass 
•   Installed/uninstalled Cordova with npm via ‘npm install cordova@rc’. 
Pass
•   Verified ability to update Cordova from older version Pass
•   Verified ability to create Cordova app with windows and wp8 platforms 
(--usenpm / --usegit flags)
•   Built app for different archs (x86, x64, arm, anycpu). Pass
•   Ran app with target keys and vers

-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com] 
Sent: Thursday, November 13, 2014 7:25 AM
To: dev@cordova.apache.org
Subject: Re: [VOTE] Tools Release, take 3

Ray Camden wrote:
> To update your tools:
>
> npm install -g cordova
> npm install -g plugman
>
> To be clear, a "regular" user doesn't need to update plugman, right?

I think there is a workflow where a regular user uses `plugman` directly (I 
think it's probably one where you aren't using cordova, but instead use 
cordova-{platform}/bin/create and friends).

Otherwise, if you only use `cordova` directly, then the plugman it uses would 
be updated automatically by updating cordova, and you'd be fine.

Afaiu, there are three workflows:
1. Plugin author — uses plugman directly 2. Single-platform writer — 
potentially uses plugman directly 3. Multiplatform writer — uses cordova (and 
everything else is used
indirectly)

The instructions would probably benefit from "if you have foo installed, use X 
to update it".

B CB  [  
X  ܚX KK[XZ[
 ] ][  X  ܚX P ܙݘK \X K ܙ B  ܈Y][ۘ[  [X[  K[XZ[
 ] Z[ ܙݘK \X K ܙ B

Re: [VOTE] Tools Release, take 3

[Ray Camden]

+1 to this. That was my first though - a ‘regular’ user may be confused
and think they need to get this when they don’t.

On 11/13/14, 9:24 AM, "Josh Soref"  wrote:

>Ray Camden wrote:
>>
>The instructions would probably benefit from "if you have foo installed,
>use X to update it".
>
>?B�CB�
>?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?�ܙ?ݘK�\?X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�
>?�??K[XZ[?�??]�Z?[???�ܙ?ݘK�\?X�?K�ܙ�B


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Tools Release, take 3

[Josh Soref]

Ray Camden wrote:
> To update your tools:
>
> npm install -g cordova
> npm install -g plugman
>
> To be clear, a "regular" user doesn't need to update plugman, right?

I think there is a workflow where a regular user uses `plugman` directly
(I think it's probably one where you aren't using cordova, but instead use
cordova-{platform}/bin/create and friends).

Otherwise, if you only use `cordova` directly, then the plugman it uses
would be updated automatically by updating cordova, and you'd be fine.

Afaiu, there are three workflows:
1. Plugin author — uses plugman directly
2. Single-platform writer — potentially uses plugman directly
3. Multiplatform writer — uses cordova (and everything else is used
indirectly)

The instructions would probably benefit from "if you have foo installed,
use X to update it".

Re: [VOTE] Tools Release, take 3

[Mark Koudritsky]

On Thu, Nov 13, 2014 at 10:06 AM, Ray Camden  wrote:

> Mark, question about this:
>
> To update your tools:
>
> npm install -g cordova
> npm install -g plugman
>
>
> To be clear, a Œregular¹ user doesn¹t need to update plugman, right?
>
>
At present the plugman npm package contains only the CLI tool for using the
"plugman" command from command line. All the logic lives in cordova-lib.
When you npm install cordova, plugman is not installed. So if you or your
scrips don't explicitly call plugman, you don't need to install it.

Re: [VOTE] Tools Release, take 3

[Ray Camden]

Mark, question about this:

To update your tools:

npm install -g cordova
npm install -g plugman


To be clear, a Œregular¹ user doesn¹t need to update plugman, right?


On 11/12/14, 10:47 AM, "Mark Koudritsky"  wrote:

>Please also review the updated blog post:
>https://github.com/cordova/apache-blog-posts/blob/master/2014-11-10-tools-
>release.md


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Tools Release, take 3

[Mark Koudritsky]

Please also review the updated blog post:
https://github.com/cordova/apache-blog-posts/blob/master/2014-11-10-tools-release.md