On Wed, Sep 12, 2018 at 12:29 PM Chris Brody <chris.br...@gmail.com> wrote: > > Potentially controversial proposal. > > For example: https://github.com/apache/cordova-create/pull/31 > > The proposal is that Cordova packages in the master branch should > depend on nightly builds, not on old patch release. > > If accepted, I think we should apply a similar change to the master > branch of all other Cordova tools and platform packages. > > I think this would give us better integrity of nightly builds.
We should not need to make any changes to the master branch for nightlies to point at other nightlies. As part of the nightly build process, all the other cordova dependencies of each module are updated to point to the equivalent nightly versions. So cordova-cli@nightly-x.y.z is using cordova-create@nightly-x.y.z and cordova-lib@nightly-x.y.z and cordova-common@nightly.x.y.z. They reference those explicitly, not using the "nightly" tag. We should definitely NOT be pointing anything on the master branch to specific nightly builds. It should point to whatever version (even unreleased) we depend on, with a ^ caret so npm will grab the latest. Reminder that nightly builds are for Cordova developer testing, not for use by end users because they are not approved releases per Apache policy. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
