On Wed, Sep 12, 2018, 4:35 PM Jesse <purplecabb...@gmail.com> wrote: > nightly is just master on any given 'night' right? >
Yes, that is my understanding. We don't want to update dependent versions of everything all the time ... > Agreed. My proposal would use the caret (^) character in the nightly dependency versions to automatically use the latest nightly build of each Cordova dependency (in master branch). I think, if anything, what is needed is an overall test of all the pieces > together, but I don't think this means modifying every package.json of > every module every night. > That is exactly what my proposal aims to accomplish. If we wanted more flexibility, maybe the git-master version of each > package.json points at the git-master of each other module ... but I don't > think this helps us. > That would have been a worthwhile solution if we did not have the nightly packages published on npm. Since we do have the nightly packages published on npm then yes that idea is not needed. I think is is best to just expect that things are going to break, Yes and we will have to resolve dependencies when we choose to release. > As I said before: according to my proposal we should be able to drop the "-nightly*" part from dependency versions when making major releases. The one criticism that I would agree with is that I don't see anyone else working quite this way. If this proposal is accepted I think it should be documented thoroughly and carefully. In case this proposal is accepted, I am thinking we may want to rename the default branch to something like "edge", "dev", or "unstable" to better reflect the actual less-stable situation.
