[Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Andrew Grieve <ag...@chromium.org>]

Please review and vote on the release of cordova@3.4.0-0.1.1 and
plugman@0.20.0 to NPM.
Release issue: https://issues.apache.org/jira/browse/CB-6115
Both cordova and plugman have been uploaded to npm with the "rc" tag:
npm install -g cordova@rc    npm install -g plugman@rc
The packages were published from their corresponding git tags:    plugman:
0.20.0 (de94c77361b65f363d008f620397c548c6feb113)    cli: 3.4.0-0.1.1
(bf4383c16a038b81669797681f25d59419db8dcd)
Upon a successful vote, I will tag the releases as "latest" on NPM and post
the corresponding blog post.
Voting will go on for 48 hours.

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Andrew Grieve <ag...@chromium.org>]

Thanks Bryan!

I think that's enough to retract my +1. I'll try and fix it up and post
another RC.


On Mon, Mar 3, 2014 at 9:42 AM, Bryan Higgins <br...@bryanhiggins.net>wrote:

> I found another issue which may actually be a show stopper.
>
> Any plugins added prior to adding a platform are not included in that
> platform.
>
> This is a regression from 3.4.0-0.1.0
>
> https://issues.apache.org/jira/browse/CB-6151
>
>
> On Sun, Mar 2, 2014 at 3:30 PM, Carlos Santana <cs...@gmail.com>
> wrote:
>
> > How do we handle dependencies for cordova-cli and plugman once you put
> them
> > in /dist/ ?
> >
> > These tools don't work if user doesn't get/install the dependencies
> >
> > I have being looking for more information on these with no luck on what
> > should be the best way to handle it for cordova.
> >
> > So far I have found two projects "struts" [1] and "maven" [2],
> > Each one has a document/html explaining for end users what is the
> > dependency graph and information about each dependency (Version, License,
> > and Location to Get it)
> >
> > I know we use npm to install and resolved dependencies but I think we
> could
> > start by documenting for end users what are the dependencies that the
> > cordova-cli and plugman need to be able to run.
> > Maybe start with a simple table with the dependency graph, version,
> license
> > type (i.e. GPLv2, MIT, Apache 2.0, etc..) and the npm uri and repo uri
> and
> > hash.
> >
> > We could also looked into providing a a convenient "binary"
> > cordova-cli-3.4.0.-1.0.1-npmbundle.tgz that includes all the dependencies
> > bundled (i.e. npm pack) [3]
> >
> > 1:
> >
> http://maven.apache.org/wagon/wagon-providers/wagon-ftp/dependencies.html
> > 2: http://struts.apache.org/release/2.3.x/struts2-core/dependencies.html
> > 3: https://www.npmjs.org/doc/cli/npm-pack.html
> >
> >
> >
> >
> >
> >
> > On Fri, Feb 28, 2014 at 12:13 PM, Andrew Grieve <agrieve@chromium.org
> > >wrote:
> >
> > > Yes, that's my goal.
> > >
> > >
> > > On Fri, Feb 28, 2014 at 11:09 AM, Marcel Kinard <cm...@gmail.com>
> > > wrote:
> > >
> > > > To ask the question a bit differently, why is released code not going
> > to
> > > > dist? Additional channels are fine, but the channels should always
> > > include
> > > > dist, right?
> > > >
> > > > My intention in asking this question is to not force a vote, but for
> > > > consumers to find all Apache-released software on dist. Or do I
> > > > misunderstand the role of dist? I'm looking at the sections "Where do
> > > > releases go" and "Where can we host public (GA) releases" of
> > > > http://www.apache.org/dev/release
> > > >
> > > > Or are the tools and plugins not considered "released code"?
> > > >
> > > > (I can hear the moans already, just trying to keep us honest.)
> > > >
> > > > Andrew, do I understand that you'll be posting tools and plugins to
> > dist?
> > > >
> > > > On Feb 27, 2014, at 11:51 AM, Brian LeRoux <b...@brian.io> wrote:
> > > >
> > > > > We do not have to vote on code not on /dist.
> > > > > On Feb 27, 2014 8:47 AM, "Andrew Grieve" <ag...@chromium.org>
> > wrote:
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Carlos Santana
> > <cs...@gmail.com>
> >
>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Bryan Higgins <br...@bryanhiggins.net>]

I found another issue which may actually be a show stopper.

Any plugins added prior to adding a platform are not included in that
platform.

This is a regression from 3.4.0-0.1.0

https://issues.apache.org/jira/browse/CB-6151


On Sun, Mar 2, 2014 at 3:30 PM, Carlos Santana <cs...@gmail.com> wrote:

> How do we handle dependencies for cordova-cli and plugman once you put them
> in /dist/ ?
>
> These tools don't work if user doesn't get/install the dependencies
>
> I have being looking for more information on these with no luck on what
> should be the best way to handle it for cordova.
>
> So far I have found two projects "struts" [1] and "maven" [2],
> Each one has a document/html explaining for end users what is the
> dependency graph and information about each dependency (Version, License,
> and Location to Get it)
>
> I know we use npm to install and resolved dependencies but I think we could
> start by documenting for end users what are the dependencies that the
> cordova-cli and plugman need to be able to run.
> Maybe start with a simple table with the dependency graph, version, license
> type (i.e. GPLv2, MIT, Apache 2.0, etc..) and the npm uri and repo uri and
> hash.
>
> We could also looked into providing a a convenient "binary"
> cordova-cli-3.4.0.-1.0.1-npmbundle.tgz that includes all the dependencies
> bundled (i.e. npm pack) [3]
>
> 1:
> http://maven.apache.org/wagon/wagon-providers/wagon-ftp/dependencies.html
> 2: http://struts.apache.org/release/2.3.x/struts2-core/dependencies.html
> 3: https://www.npmjs.org/doc/cli/npm-pack.html
>
>
>
>
>
>
> On Fri, Feb 28, 2014 at 12:13 PM, Andrew Grieve <agrieve@chromium.org
> >wrote:
>
> > Yes, that's my goal.
> >
> >
> > On Fri, Feb 28, 2014 at 11:09 AM, Marcel Kinard <cm...@gmail.com>
> > wrote:
> >
> > > To ask the question a bit differently, why is released code not going
> to
> > > dist? Additional channels are fine, but the channels should always
> > include
> > > dist, right?
> > >
> > > My intention in asking this question is to not force a vote, but for
> > > consumers to find all Apache-released software on dist. Or do I
> > > misunderstand the role of dist? I'm looking at the sections "Where do
> > > releases go" and "Where can we host public (GA) releases" of
> > > http://www.apache.org/dev/release
> > >
> > > Or are the tools and plugins not considered "released code"?
> > >
> > > (I can hear the moans already, just trying to keep us honest.)
> > >
> > > Andrew, do I understand that you'll be posting tools and plugins to
> dist?
> > >
> > > On Feb 27, 2014, at 11:51 AM, Brian LeRoux <b...@brian.io> wrote:
> > >
> > > > We do not have to vote on code not on /dist.
> > > > On Feb 27, 2014 8:47 AM, "Andrew Grieve" <ag...@chromium.org>
> wrote:
> > >
> > >
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Carlos Santana <cs...@gmail.com>]

How do we handle dependencies for cordova-cli and plugman once you put them
in /dist/ ?

These tools don't work if user doesn't get/install the dependencies

I have being looking for more information on these with no luck on what
should be the best way to handle it for cordova.

So far I have found two projects "struts" [1] and "maven" [2],
Each one has a document/html explaining for end users what is the
dependency graph and information about each dependency (Version, License,
and Location to Get it)

I know we use npm to install and resolved dependencies but I think we could
start by documenting for end users what are the dependencies that the
cordova-cli and plugman need to be able to run.
Maybe start with a simple table with the dependency graph, version, license
type (i.e. GPLv2, MIT, Apache 2.0, etc..) and the npm uri and repo uri and
hash.

We could also looked into providing a a convenient "binary"
cordova-cli-3.4.0.-1.0.1-npmbundle.tgz that includes all the dependencies
bundled (i.e. npm pack) [3]

1: http://maven.apache.org/wagon/wagon-providers/wagon-ftp/dependencies.html
2: http://struts.apache.org/release/2.3.x/struts2-core/dependencies.html
3: https://www.npmjs.org/doc/cli/npm-pack.html






On Fri, Feb 28, 2014 at 12:13 PM, Andrew Grieve <ag...@chromium.org>wrote:

> Yes, that's my goal.
>
>
> On Fri, Feb 28, 2014 at 11:09 AM, Marcel Kinard <cm...@gmail.com>
> wrote:
>
> > To ask the question a bit differently, why is released code not going to
> > dist? Additional channels are fine, but the channels should always
> include
> > dist, right?
> >
> > My intention in asking this question is to not force a vote, but for
> > consumers to find all Apache-released software on dist. Or do I
> > misunderstand the role of dist? I'm looking at the sections "Where do
> > releases go" and "Where can we host public (GA) releases" of
> > http://www.apache.org/dev/release
> >
> > Or are the tools and plugins not considered "released code"?
> >
> > (I can hear the moans already, just trying to keep us honest.)
> >
> > Andrew, do I understand that you'll be posting tools and plugins to dist?
> >
> > On Feb 27, 2014, at 11:51 AM, Brian LeRoux <b...@brian.io> wrote:
> >
> > > We do not have to vote on code not on /dist.
> > > On Feb 27, 2014 8:47 AM, "Andrew Grieve" <ag...@chromium.org> wrote:
> >
> >
>



-- 
Carlos Santana
<cs...@gmail.com>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Andrew Grieve <ag...@chromium.org>]

Yes, that's my goal.


On Fri, Feb 28, 2014 at 11:09 AM, Marcel Kinard <cm...@gmail.com> wrote:

> To ask the question a bit differently, why is released code not going to
> dist? Additional channels are fine, but the channels should always include
> dist, right?
>
> My intention in asking this question is to not force a vote, but for
> consumers to find all Apache-released software on dist. Or do I
> misunderstand the role of dist? I'm looking at the sections "Where do
> releases go" and "Where can we host public (GA) releases" of
> http://www.apache.org/dev/release
>
> Or are the tools and plugins not considered "released code"?
>
> (I can hear the moans already, just trying to keep us honest.)
>
> Andrew, do I understand that you'll be posting tools and plugins to dist?
>
> On Feb 27, 2014, at 11:51 AM, Brian LeRoux <b...@brian.io> wrote:
>
> > We do not have to vote on code not on /dist.
> > On Feb 27, 2014 8:47 AM, "Andrew Grieve" <ag...@chromium.org> wrote:
>
>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Marcel Kinard <cm...@gmail.com>]

To ask the question a bit differently, why is released code not going to dist? Additional channels are fine, but the channels should always include dist, right?

My intention in asking this question is to not force a vote, but for consumers to find all Apache-released software on dist. Or do I misunderstand the role of dist? I'm looking at the sections "Where do releases go" and "Where can we host public (GA) releases" of http://www.apache.org/dev/release

Or are the tools and plugins not considered "released code"?

(I can hear the moans already, just trying to keep us honest.)

Andrew, do I understand that you'll be posting tools and plugins to dist?

On Feb 27, 2014, at 11:51 AM, Brian LeRoux <b...@brian.io> wrote:

> We do not have to vote on code not on /dist.
> On Feb 27, 2014 8:47 AM, "Andrew Grieve" <ag...@chromium.org> wrote:

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Josh Soref <js...@blackberry.com>]

Michal Mocny wrote:
> If its a significant regression, then of course.
>
> Whats the issue?  Perhaps you shouldn't hold back your vote if its really
> worth a -1!  I created a sample project and seemed fine for iOS/Android.
> Also tried it with our cca toolkit just fine.

Many variations of adding/removing plugins (especially testing using
cordova-mobile-spec) resulted in errors.

I¹ve patched a bunch of them, at least one is still open (w/ patch), and I
have one or two bugs left to file.

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Michal Mocny <mm...@chromium.org>]

If its a significant regression, then of course.

Whats the issue?  Perhaps you shouldn't hold back your vote if its really
worth a -1!  I created a sample project and seemed fine for iOS/Android.
 Also tried it with our cca toolkit just fine.

-Michal

On Thu, Feb 27, 2014 at 3:48 PM, Josh Soref <js...@blackberry.com> wrote:

> Michal Mocny wrote:
> >That isn't really criteria for a -1.  Someone summed it up in another
> >thread: no release is perfect, but if its better than the last one, +1.
>
> But if this is a rewrite that is actually a regression from the previous
> version, then perhaps this is actually a really valid case for a -1? :)
>
>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Josh Soref <js...@blackberry.com>]

Michal Mocny wrote:
>That isn't really criteria for a -1.  Someone summed it up in another
>thread: no release is perfect, but if its better than the last one, +1.

But if this is a rewrite that is actually a regression from the previous
version, then perhaps this is actually a really valid case for a -1? :)

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Michal Mocny <mm...@chromium.org>]

On Thu, Feb 27, 2014 at 2:06 PM, Josh Soref <js...@blackberry.com> wrote:

> Andrew Grieve wrote:
>
> > My understanding is (I believe) the same as what Josh said:
>
> Yes, I believe we¹re on the same page
>
> > http://www.apache.org/dev/release#what does not mention being on dist/
> >
> > http://www.apache.org/dev/release#where-do-releases-go does mention it,
>
> > but says that releasing to things like Maven (e.g. npm) can happen only
>
> > After putting a release on dist/
> >
> > I'll work on getting it on dist/ and then we can resume voting?
>
> Sounds good. I¹m still going to refrain from voting.
>
> And note that right now I¹m -1 on plugman because I expect to file another
> 3-10 bugs+PRs for it today.
>

That isn't really criteria for a -1.  Someone summed it up in another
thread: no release is perfect, but if its better than the last one, +1.

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Josh Soref <js...@blackberry.com>]

Andrew Grieve wrote:

> My understanding is (I believe) the same as what Josh said:

Yes, I believe we¹re on the same page

> http://www.apache.org/dev/release#what does not mention being on dist/
>
> http://www.apache.org/dev/release#where-do-releases-go does mention it,

> but says that releasing to things like Maven (e.g. npm) can happen only

> After putting a release on dist/
>
> I'll work on getting it on dist/ and then we can resume voting?

Sounds good. I¹m still going to refrain from voting.

And note that right now I¹m -1 on plugman because I expect to file another
3-10 bugs+PRs for it today.

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Andrew Grieve <ag...@chromium.org>]

My understanding is (I believe) the same as what Josh said:

http://www.apache.org/dev/release#what does not mention being on dist/

http://www.apache.org/dev/release#where-do-releases-go does mention it, but
says that releasing to things like Maven (e.g. npm) can happen only after
putting a release on dist/

I'll work on getting it on dist/ and then we can resume voting?


On Thu, Feb 27, 2014 at 1:19 PM, Brian LeRoux <b...@brian.io> wrote:

> Right, but the vote is on stuff that is in ./dist from what I've been able
> to tease from the mountains of email on this important topic.
>
> The point isn't really to vote. It to verify sha's on /dist is an action of
> the PMC.
>
> Though indeed voting seems kind of silly when you put in that perspective
> since computers can (and probably should) do that soft of job.
>
>
> On Thu, Feb 27, 2014 at 10:08 AM, Andrew Grieve <agrieve@chromium.org
> >wrote:
>
> > My understanding from all of the discussion & from what Joe pointed out
> is
> > that we do need to vote.
> > It's not hard to put a copy on dist/ as well.
> >
> >
> > On Thu, Feb 27, 2014 at 12:03 PM, Joe Schaefer <joe_schaefer@yahoo.com
> > >wrote:
> >
> > > I don't doubt there is some impedance mismatch between
> > > the different types of distributions and channels you guys
> > > use and what the policy calls for, but as the document says
> > > deviations need to be approved by the board.  All I can say
> > > is that we've been down this road with other projects and
> > > ultimately all of them (maven was the most challenging) have
> > > complied with policy.
> > >
> > >
> > >
> > >
> > > On Thursday, February 27, 2014 12:00 PM, Josh Soref <
> > jsoref@blackberry.com>
> > > wrote:
> > >
> > > Joe Schaefer wrote:
> > > >
> > > >> Well I wouldn't put it quite like that.  Anything that
> > > >> meets the definition of a release *should* be on dist
> > > >> anyway.  The definition I am referring to is here:
> > > >>
> > > >> http://www.apache.org/dev/release#what
> > > >
> > > >That¹s problematic.
> > > >
> > > >> Where do releases go?
> > > >> A release isn't 'released' until the contents are in the project's
> > > >>distribution directory,
> > > >> which is a subdirectory of www.apache.org/dist/.
> > > >
> > > >> In addition to the distribution directory,
> > > >> project that use Maven or a related build tool sometimes place their
> > > >>releases on
> > > >> repository.apache.org beside some convenience binaries.
> > > >> The distribution directory is required, while the repository system
> is
> > > >>an optional convenience.
> > > >
> > > >This implies that we¹re required to have plugman (or whatever) in
> dist/
> > > >(before?) it lands in npm¹s repo.
> > > >
> > > >
> > > >Note: I¹m not advocating anything, just following to logical
> > conclusions.
> > > >Voting and releasing is a headache which I am currently leaving to
> > others.
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Brian LeRoux <b...@brian.io>]

Right, but the vote is on stuff that is in ./dist from what I've been able
to tease from the mountains of email on this important topic.

The point isn't really to vote. It to verify sha's on /dist is an action of
the PMC.

Though indeed voting seems kind of silly when you put in that perspective
since computers can (and probably should) do that soft of job.


On Thu, Feb 27, 2014 at 10:08 AM, Andrew Grieve <ag...@chromium.org>wrote:

> My understanding from all of the discussion & from what Joe pointed out is
> that we do need to vote.
> It's not hard to put a copy on dist/ as well.
>
>
> On Thu, Feb 27, 2014 at 12:03 PM, Joe Schaefer <joe_schaefer@yahoo.com
> >wrote:
>
> > I don't doubt there is some impedance mismatch between
> > the different types of distributions and channels you guys
> > use and what the policy calls for, but as the document says
> > deviations need to be approved by the board.  All I can say
> > is that we've been down this road with other projects and
> > ultimately all of them (maven was the most challenging) have
> > complied with policy.
> >
> >
> >
> >
> > On Thursday, February 27, 2014 12:00 PM, Josh Soref <
> jsoref@blackberry.com>
> > wrote:
> >
> > Joe Schaefer wrote:
> > >
> > >> Well I wouldn't put it quite like that.  Anything that
> > >> meets the definition of a release *should* be on dist
> > >> anyway.  The definition I am referring to is here:
> > >>
> > >> http://www.apache.org/dev/release#what
> > >
> > >That¹s problematic.
> > >
> > >> Where do releases go?
> > >> A release isn't 'released' until the contents are in the project's
> > >>distribution directory,
> > >> which is a subdirectory of www.apache.org/dist/.
> > >
> > >> In addition to the distribution directory,
> > >> project that use Maven or a related build tool sometimes place their
> > >>releases on
> > >> repository.apache.org beside some convenience binaries.
> > >> The distribution directory is required, while the repository system is
> > >>an optional convenience.
> > >
> > >This implies that we¹re required to have plugman (or whatever) in dist/
> > >(before?) it lands in npm¹s repo.
> > >
> > >
> > >Note: I¹m not advocating anything, just following to logical
> conclusions.
> > >Voting and releasing is a headache which I am currently leaving to
> others.
> > >
> > >
> > >
> > >
> >
>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Michal Mocny <mm...@chromium.org>]

+1


On Thu, Feb 27, 2014 at 1:08 PM, Andrew Grieve <ag...@chromium.org> wrote:

> My understanding from all of the discussion & from what Joe pointed out is
> that we do need to vote.
> It's not hard to put a copy on dist/ as well.
>
>
> On Thu, Feb 27, 2014 at 12:03 PM, Joe Schaefer <joe_schaefer@yahoo.com
> >wrote:
>
> > I don't doubt there is some impedance mismatch between
> > the different types of distributions and channels you guys
> > use and what the policy calls for, but as the document says
> > deviations need to be approved by the board.  All I can say
> > is that we've been down this road with other projects and
> > ultimately all of them (maven was the most challenging) have
> > complied with policy.
> >
> >
> >
> >
> > On Thursday, February 27, 2014 12:00 PM, Josh Soref <
> jsoref@blackberry.com>
> > wrote:
> >
> > Joe Schaefer wrote:
> > >
> > >> Well I wouldn't put it quite like that.  Anything that
> > >> meets the definition of a release *should* be on dist
> > >> anyway.  The definition I am referring to is here:
> > >>
> > >> http://www.apache.org/dev/release#what
> > >
> > >That¹s problematic.
> > >
> > >> Where do releases go?
> > >> A release isn't 'released' until the contents are in the project's
> > >>distribution directory,
> > >> which is a subdirectory of www.apache.org/dist/.
> > >
> > >> In addition to the distribution directory,
> > >> project that use Maven or a related build tool sometimes place their
> > >>releases on
> > >> repository.apache.org beside some convenience binaries.
> > >> The distribution directory is required, while the repository system is
> > >>an optional convenience.
> > >
> > >This implies that we¹re required to have plugman (or whatever) in dist/
> > >(before?) it lands in npm¹s repo.
> > >
> > >
> > >Note: I¹m not advocating anything, just following to logical
> conclusions.
> > >Voting and releasing is a headache which I am currently leaving to
> others.
> > >
> > >
> > >
> > >
> >
>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Andrew Grieve <ag...@chromium.org>]

My understanding from all of the discussion & from what Joe pointed out is
that we do need to vote.
It's not hard to put a copy on dist/ as well.


On Thu, Feb 27, 2014 at 12:03 PM, Joe Schaefer <jo...@yahoo.com>wrote:

> I don't doubt there is some impedance mismatch between
> the different types of distributions and channels you guys
> use and what the policy calls for, but as the document says
> deviations need to be approved by the board.  All I can say
> is that we've been down this road with other projects and
> ultimately all of them (maven was the most challenging) have
> complied with policy.
>
>
>
>
> On Thursday, February 27, 2014 12:00 PM, Josh Soref <js...@blackberry.com>
> wrote:
>
> Joe Schaefer wrote:
> >
> >> Well I wouldn't put it quite like that.  Anything that
> >> meets the definition of a release *should* be on dist
> >> anyway.  The definition I am referring to is here:
> >>
> >> http://www.apache.org/dev/release#what
> >
> >That¹s problematic.
> >
> >> Where do releases go?
> >> A release isn't 'released' until the contents are in the project's
> >>distribution directory,
> >> which is a subdirectory of www.apache.org/dist/.
> >
> >> In addition to the distribution directory,
> >> project that use Maven or a related build tool sometimes place their
> >>releases on
> >> repository.apache.org beside some convenience binaries.
> >> The distribution directory is required, while the repository system is
> >>an optional convenience.
> >
> >This implies that we¹re required to have plugman (or whatever) in dist/
> >(before?) it lands in npm¹s repo.
> >
> >
> >Note: I¹m not advocating anything, just following to logical conclusions.
> >Voting and releasing is a headache which I am currently leaving to others.
> >
> >
> >
> >
>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Joe Schaefer <jo...@yahoo.com>]

I don't doubt there is some impedance mismatch between
the different types of distributions and channels you guys
use and what the policy calls for, but as the document says
deviations need to be approved by the board.  All I can say
is that we've been down this road with other projects and
ultimately all of them (maven was the most challenging) have
complied with policy.




On Thursday, February 27, 2014 12:00 PM, Josh Soref <js...@blackberry.com> wrote:
 
Joe Schaefer wrote:
>
>> Well I wouldn't put it quite like that.  Anything that
>> meets the definition of a release *should* be on dist
>> anyway.  The definition I am referring to is here:
>>
>> http://www.apache.org/dev/release#what
>
>That¹s problematic.
>
>> Where do releases go?
>> A release isn't 'released' until the contents are in the project's
>>distribution directory,
>> which is a subdirectory of www.apache.org/dist/.
>
>> In addition to the distribution directory,
>> project that use Maven or a related build tool sometimes place their
>>releases on
>> repository.apache.org beside some convenience binaries.
>> The distribution directory is required, while the repository system is
>>an optional convenience.
>
>This implies that we¹re required to have plugman (or whatever) in dist/
>(before?) it lands in npm¹s repo.
>
>
>Note: I¹m not advocating anything, just following to logical conclusions.
>Voting and releasing is a headache which I am currently leaving to others.
>
>
>
>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Josh Soref <js...@blackberry.com>]

Joe Schaefer wrote:
> Well I wouldn't put it quite like that.  Anything that
> meets the definition of a release *should* be on dist
> anyway.  The definition I am referring to is here:
>
> http://www.apache.org/dev/release#what

That¹s problematic.

> Where do releases go?
> A release isn't 'released' until the contents are in the project's
>distribution directory,
> which is a subdirectory of www.apache.org/dist/.

> In addition to the distribution directory,
> project that use Maven or a related build tool sometimes place their
>releases on
> repository.apache.org beside some convenience binaries.
> The distribution directory is required, while the repository system is
>an optional convenience.

This implies that we¹re required to have plugman (or whatever) in dist/
(before?) it lands in npm¹s repo.


Note: I¹m not advocating anything, just following to logical conclusions.
Voting and releasing is a headache which I am currently leaving to others.

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Joe Schaefer <jo...@yahoo.com>]

Well I wouldn't put it quite like that.  Anything that
meets the definition of a release *should* be on dist
anyway.  The definition I am referring to is here:

http://www.apache.org/dev/release#what

HTH



On Thursday, February 27, 2014 11:52 AM, Brian LeRoux <b...@brian.io> wrote:
 
We do not have to vote on code not on /dist.
>
>On Feb 27, 2014 8:47 AM, "Andrew Grieve" <ag...@chromium.org> wrote:
>
>> Please review and vote on the release of cordova@3.4.0-0.1.1 and
>> plugman@0.20.0 to NPM.
>> Release issue: https://issues.apache.org/jira/browse/CB-6115
>> Both cordova and plugman have been uploaded to npm with the "rc" tag:
>> npm install -g cordova@rc    npm install -g plugman@rc
>> The packages were published from their corresponding git tags:    plugman:
>> 0.20.0 (de94c77361b65f363d008f620397c548c6feb113)    cli: 3.4.0-0.1.1
>> (bf4383c16a038b81669797681f25d59419db8dcd)
>> Upon a successful vote, I will tag the releases as "latest" on NPM and post
>> the corresponding blog post.
>> Voting will go on for 48 hours.
>>
>
>
>

Re: [Vote] cordova@3.4.0-0.1.1 plugman@0.20.0

[Brian LeRoux <b...@brian.io>]

We do not have to vote on code not on /dist.
 On Feb 27, 2014 8:47 AM, "Andrew Grieve" <ag...@chromium.org> wrote:

> Please review and vote on the release of cordova@3.4.0-0.1.1 and
> plugman@0.20.0 to NPM.
> Release issue: https://issues.apache.org/jira/browse/CB-6115
> Both cordova and plugman have been uploaded to npm with the "rc" tag:
> npm install -g cordova@rc    npm install -g plugman@rc
> The packages were published from their corresponding git tags:    plugman:
> 0.20.0 (de94c77361b65f363d008f620397c548c6feb113)    cli: 3.4.0-0.1.1
> (bf4383c16a038b81669797681f25d59419db8dcd)
> Upon a successful vote, I will tag the releases as "latest" on NPM and post
> the corresponding blog post.
> Voting will go on for 48 hours.
>