I prefer a minor CLI release that just pins the recently released platforms
(or in progress of being released) and no other changes.

The other proposed changes sounds good, but for a future major release with
no rush.

El mié., 8 ago. 2018 a las 14:07, Jan Piotrowski (<piotrow...@gmail.com>)
escribió:

> You are talking about Cordova CLI, correct?
>
> Do you only want to release a new CLI or also the other stuff?
>
> What about the platforms - major or minor releases?
> What about core plugins - major or minor releases?
>
> Maybe I misunderstood, but why rush all this instead of just do the work in
> all the repo's `master`, then release when the actual platforms and plugins
> are ready, then do a CLI release when justified?
>
> -J
>
>
>
> 2018-08-08 13:42 GMT+02:00 Chris Brody <chris.br...@gmail.com>:
>
> > I would like to propose the following idea: make a major Cordova
> > release (Cordova 9), based on what was already published for Cordova
> > 8, with a very limited set of changes such as:
> > * drop Node.js 4 support
> > * remove committed node_modules from all supported Cordova platforms
> > * commit package-lock.json
> > * update dependencies (should resolve the npm audit issues if done right)
> > * drop support for Xcode pre-9 on both iOS and cordova-osx
> >
> > and maybe some other items such as:
> > * cordova-android patch release discussed in the thread at:
> > https://bit.ly/2vpUbSS
> > * add iOS bridge WebView as proposed in
> > https://github.com/apache/cordova-docs/pull/867
> > * drop iOS pre-10 support
> >
> > This idea should give us a double benefit:
> > * drop burden of old Node.js 4, Xcode pre-9, and maybe iOS pre-10
> > support almost immediately
> > * less pressure to cut a major release off the master branches
> >
> > This would entail making a new release branch per repo, sometimes
> > based on master and sometimes based on another release branch, and
> > then increasing to the subsequent major release -dev version on
> > master.
> >
> > I will probably need 1-2 weeks to finish something for a client then
> > can work on this one.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

Reply via email to