We pin the platform versions with ~, so as next cordova-android is a patch version it will be picked once released. (If we update this to ~7.1.0 https://github.com/apache/cordova-lib/blob/master/src/platforms/platformsConfig.json#L18). No need to delay a lib release because of that.
I have not ignored your release reviews vote threads, I just don't have experience with those platforms, so I don't vote if I can't really know it's right. Probably others do the same. Also it's August and a lot of people is on holiday, so there is even less people than usual. El mié., 8 ago. 2018 a las 14:24, Chris Brody (<chris.br...@gmail.com>) escribió: > I am fine to continue with the cordova-fetch, cordova-lib, and > cordova-cli patch releases needed to do the following: > * fix repo url in cordova-fetch as already proposed in > https://github.com/apache/cordova-fetch/pull/38 > * cordova-lib pins the released platforms and resolve audit issues > * cordova-cli > > If someone makes another cordova-android patch release I would be > happy to pin it at the same time. > > I am currently blocked since my requests for release review votes have > been consistently ignored. > On Wed, Aug 8, 2018 at 8:11 AM julio cesar sanchez > <jcesarmob...@gmail.com> wrote: > > > > 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 > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
