You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Ian Clelland <ic...@chromium.org> on 2014/06/11 14:41:31 UTC
[DISCUSS] Tools release
With the bump to cordova-lib, which, incidentally, also includes my
favorite feature ever -- support for Android library projects -- I'd like
to start a vote so that we can get that out to NPM.
Proposed release code:
cordova-lib 0.21.4 -- already tagged at commit c7e46c8
cordova-plugman 0.22.3 -- to be based on commit b40efa6, with a new version
and a dependency on -lib 0.21.4
cordova-cli 3.5.0-0.2.5 -- to be based on commit 46cde90, with a new
version and a dependency on -lib 0.21.4
Does anyone have any issues with me making those commits, building the
artifacts and starting the vote process? Any outstanding (hopefully minor)
patches to land?
I volunteer to be the release manager for this release.
Ian
Re: [DISCUSS] Tools release
Posted by Andrew Grieve <ag...@chromium.org>.
Now that the dust has settled on the android library change, I'd like to
try this again. Created bug:
https://issues.apache.org/jira/browse/CB-7002
I hope to put together RCs tomorrow morning. Likely not too many people
checking email any more since it's the weekend, but feeling like we're
overdue on this, so hopefully Monday we can all test & vote. If it doesn't
pan out, oh well, but otherwise we'll have a release! :)
On Thu, Jun 12, 2014 at 1:44 AM, Anis KADRI <an...@gmail.com> wrote:
> On Wed, Jun 11, 2014 at 6:19 AM, Ian Clelland <ic...@chromium.org>
> wrote:
>
> > (FWIW, I don't see any reason *not* to consider it end-user software. It
> > provides the programmatic interface to all of the logic in the CLI tools.
> > If someone wanted to integrate the Cordova build process into another
> tool,
> > like an IDE or an automated build system, I would be thrilled if they
> chose
> > to use cordova-lib and called it directly from Node, rather than spawning
> > shells to invoke the CLI.)
> >
>
> +1 as well. I've played with the new flow and aside from the fact of having
> to link 3 repositories to test shit out, it works. However, I've got some
> ranting to do:
>
> Just like you said. programmatic interface to _ALL_ of the logic in the CLI
> tools even though most IDEs/tools might want to use a tiny feature of the
> CLI tools (like in Brian's case just the create-project part). There is a
> different thread on the topic and you guys seem (Google) to agree with the
> idea of a breakout but I just felt like reiterating it because I think it's
> really important for so many different reasons.
>
Re: [DISCUSS] Tools release
Posted by Anis KADRI <an...@gmail.com>.
On Wed, Jun 11, 2014 at 6:19 AM, Ian Clelland <ic...@chromium.org>
wrote:
> (FWIW, I don't see any reason *not* to consider it end-user software. It
> provides the programmatic interface to all of the logic in the CLI tools.
> If someone wanted to integrate the Cordova build process into another tool,
> like an IDE or an automated build system, I would be thrilled if they chose
> to use cordova-lib and called it directly from Node, rather than spawning
> shells to invoke the CLI.)
>
+1 as well. I've played with the new flow and aside from the fact of having
to link 3 repositories to test shit out, it works. However, I've got some
ranting to do:
Just like you said. programmatic interface to _ALL_ of the logic in the CLI
tools even though most IDEs/tools might want to use a tiny feature of the
CLI tools (like in Brian's case just the create-project part). There is a
different thread on the topic and you guys seem (Google) to agree with the
idea of a breakout but I just felt like reiterating it because I think it's
really important for so many different reasons.
Re: [DISCUSS] Tools release
Posted by Ian Clelland <ic...@chromium.org>.
I appreciate the +1 for always shipping. Thanks.
For now, the Apache situation is what it is, and shipping as fast as
possible just means starting these email threads as often as we can. I
don't want to bog the process down; I'm hoping to do a quick [DISCUSS],
then a [VOTE], and push in a couple of days.
And then maybe repeat next week, just to increase our velocity.
On Wed, Jun 11, 2014 at 9:34 AM, Brian LeRoux <b...@brian.io> wrote:
> I could debate it but I'm fatigued. Preemptive +1 for always shipping from
> me for all time.
>
> Seriously it is time to reconsider this Apache situation.
> On Jun 11, 2014 6:26 AM, "Ian Clelland" <ic...@chromium.org> wrote:
>
> > It's a library. It's published on NPM, and on dist.apache.org. It's
> > depended on by cordova-cli and cordova-plugman, which I'm proposing to
> > release simultaneously with it, and which unquestionably *are* end-user
> > software (unless you want to debate the term "end-user", but our usual
> > definition covers developers making Cordova apps.)
> >
> > Whether -lib is end-user software or not, it's a thing we release.
> >
> > Ian
> >
> >
> > (FWIW, I don't see any reason *not* to consider it end-user software. It
> > provides the programmatic interface to all of the logic in the CLI tools.
> > If someone wanted to integrate the Cordova build process into another
> tool,
> > like an IDE or an automated build system, I would be thrilled if they
> chose
> > to use cordova-lib and called it directly from Node, rather than spawning
> > shells to invoke the CLI.)
> >
> >
> > On Wed, Jun 11, 2014 at 9:00 AM, Brian LeRoux <b...@brian.io> wrote:
> >
> > > cordova-lib is not end user software..or is it?
> > > On Jun 11, 2014 5:49 AM, "Ian Clelland" <ic...@chromium.org>
> wrote:
> > >
> > > > With the bump to cordova-lib, which, incidentally, also includes my
> > > > favorite feature ever -- support for Android library projects -- I'd
> > like
> > > > to start a vote so that we can get that out to NPM.
> > > >
> > > > Proposed release code:
> > > > cordova-lib 0.21.4 -- already tagged at commit c7e46c8
> > > > cordova-plugman 0.22.3 -- to be based on commit b40efa6, with a new
> > > version
> > > > and a dependency on -lib 0.21.4
> > > > cordova-cli 3.5.0-0.2.5 -- to be based on commit 46cde90, with a new
> > > > version and a dependency on -lib 0.21.4
> > > >
> > > > Does anyone have any issues with me making those commits, building
> the
> > > > artifacts and starting the vote process? Any outstanding (hopefully
> > > minor)
> > > > patches to land?
> > > >
> > > > I volunteer to be the release manager for this release.
> > > >
> > > > Ian
> > > >
> > >
> >
>
Re: [DISCUSS] Tools release
Posted by Brian LeRoux <b...@brian.io>.
I could debate it but I'm fatigued. Preemptive +1 for always shipping from
me for all time.
Seriously it is time to reconsider this Apache situation.
On Jun 11, 2014 6:26 AM, "Ian Clelland" <ic...@chromium.org> wrote:
> It's a library. It's published on NPM, and on dist.apache.org. It's
> depended on by cordova-cli and cordova-plugman, which I'm proposing to
> release simultaneously with it, and which unquestionably *are* end-user
> software (unless you want to debate the term "end-user", but our usual
> definition covers developers making Cordova apps.)
>
> Whether -lib is end-user software or not, it's a thing we release.
>
> Ian
>
>
> (FWIW, I don't see any reason *not* to consider it end-user software. It
> provides the programmatic interface to all of the logic in the CLI tools.
> If someone wanted to integrate the Cordova build process into another tool,
> like an IDE or an automated build system, I would be thrilled if they chose
> to use cordova-lib and called it directly from Node, rather than spawning
> shells to invoke the CLI.)
>
>
> On Wed, Jun 11, 2014 at 9:00 AM, Brian LeRoux <b...@brian.io> wrote:
>
> > cordova-lib is not end user software..or is it?
> > On Jun 11, 2014 5:49 AM, "Ian Clelland" <ic...@chromium.org> wrote:
> >
> > > With the bump to cordova-lib, which, incidentally, also includes my
> > > favorite feature ever -- support for Android library projects -- I'd
> like
> > > to start a vote so that we can get that out to NPM.
> > >
> > > Proposed release code:
> > > cordova-lib 0.21.4 -- already tagged at commit c7e46c8
> > > cordova-plugman 0.22.3 -- to be based on commit b40efa6, with a new
> > version
> > > and a dependency on -lib 0.21.4
> > > cordova-cli 3.5.0-0.2.5 -- to be based on commit 46cde90, with a new
> > > version and a dependency on -lib 0.21.4
> > >
> > > Does anyone have any issues with me making those commits, building the
> > > artifacts and starting the vote process? Any outstanding (hopefully
> > minor)
> > > patches to land?
> > >
> > > I volunteer to be the release manager for this release.
> > >
> > > Ian
> > >
> >
>
Re: [DISCUSS] Tools release
Posted by Ian Clelland <ic...@chromium.org>.
It's a library. It's published on NPM, and on dist.apache.org. It's
depended on by cordova-cli and cordova-plugman, which I'm proposing to
release simultaneously with it, and which unquestionably *are* end-user
software (unless you want to debate the term "end-user", but our usual
definition covers developers making Cordova apps.)
Whether -lib is end-user software or not, it's a thing we release.
Ian
(FWIW, I don't see any reason *not* to consider it end-user software. It
provides the programmatic interface to all of the logic in the CLI tools.
If someone wanted to integrate the Cordova build process into another tool,
like an IDE or an automated build system, I would be thrilled if they chose
to use cordova-lib and called it directly from Node, rather than spawning
shells to invoke the CLI.)
On Wed, Jun 11, 2014 at 9:00 AM, Brian LeRoux <b...@brian.io> wrote:
> cordova-lib is not end user software..or is it?
> On Jun 11, 2014 5:49 AM, "Ian Clelland" <ic...@chromium.org> wrote:
>
> > With the bump to cordova-lib, which, incidentally, also includes my
> > favorite feature ever -- support for Android library projects -- I'd like
> > to start a vote so that we can get that out to NPM.
> >
> > Proposed release code:
> > cordova-lib 0.21.4 -- already tagged at commit c7e46c8
> > cordova-plugman 0.22.3 -- to be based on commit b40efa6, with a new
> version
> > and a dependency on -lib 0.21.4
> > cordova-cli 3.5.0-0.2.5 -- to be based on commit 46cde90, with a new
> > version and a dependency on -lib 0.21.4
> >
> > Does anyone have any issues with me making those commits, building the
> > artifacts and starting the vote process? Any outstanding (hopefully
> minor)
> > patches to land?
> >
> > I volunteer to be the release manager for this release.
> >
> > Ian
> >
>
Re: [DISCUSS] Tools release
Posted by Brian LeRoux <b...@brian.io>.
cordova-lib is not end user software..or is it?
On Jun 11, 2014 5:49 AM, "Ian Clelland" <ic...@chromium.org> wrote:
> With the bump to cordova-lib, which, incidentally, also includes my
> favorite feature ever -- support for Android library projects -- I'd like
> to start a vote so that we can get that out to NPM.
>
> Proposed release code:
> cordova-lib 0.21.4 -- already tagged at commit c7e46c8
> cordova-plugman 0.22.3 -- to be based on commit b40efa6, with a new version
> and a dependency on -lib 0.21.4
> cordova-cli 3.5.0-0.2.5 -- to be based on commit 46cde90, with a new
> version and a dependency on -lib 0.21.4
>
> Does anyone have any issues with me making those commits, building the
> artifacts and starting the vote process? Any outstanding (hopefully minor)
> patches to land?
>
> I volunteer to be the release manager for this release.
>
> Ian
>