Re: Food for thought over the holidays

[Filip Maj <fi...@adobe.com>]

>> What cordova-client should do to better support plugins:
>>   -Instead of considering JS the same as other assets, treat it as a
>> first-class thing.
>>   -Build cordova.js from source (check it out as a sibling to
>> cordova-ios.git)
>
>Yes.

Are you suggesting checking out cordova-js' master and building it each
time? If so, I disagree. The reason we tag the JS and need consensus on it
to go through the release ceremony is to make sure that the shared code
that is the JS works for all platforms. If we start building js from
source+master every time I think we will be introducing instability.

Re: Food for thought over the holidays

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

Moving JS into their own repositories is the motivation.

My thinking was that cordova-cli would use tags when checking out
cordova-ios, cordova-js, etc, instead of checking them out at master. When
the user wants to update to a new version, they could do "cordova update
[version]" or something like that.


On Thu, Jan 3, 2013 at 3:13 PM, Brian LeRoux <b...@brian.io> wrote:

> I thought this meant we move the JS out of CordovaJS and start moving
> it into plugin packages.
>
> On Thu, Jan 3, 2013 at 12:02 PM, Filip Maj <fi...@adobe.com> wrote:
> > time? If so, I disagree. The reason we tag the JS and need consensus on
> it
>

Re: Food for thought over the holidays

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

I thought this meant we move the JS out of CordovaJS and start moving
it into plugin packages.

On Thu, Jan 3, 2013 at 12:02 PM, Filip Maj <fi...@adobe.com> wrote:
> time? If so, I disagree. The reason we tag the JS and need consensus on it