Bumping this thread to the top. Since the number of contributions to the core grows a lot, I think we need to finally discuss the merge policy and JEP it. Will discuss it with Daniel/Oliver so that we can sync-up and come up with a proposal.
BR, Oleg среда, 28 октября 2015 г., 17:22:55 UTC+1 пользователь Jesse Glick написал: > > On Wed, Oct 28, 2015 at 12:10 PM, Baptiste Mathus <m...@batmat.net > <javascript:>> wrote: > > Jesse says that it might be preferrable to open a new squashed PR > > I never said anything of the sort. My preference remains to use plain > old Git merge and never destroy history, since simplified views of > history can always be produced on demand by using simple Git options. > But if people insist on destroying history, at least leave the PR > intact so the information is not totally lost (so long as we continue > to host on GitHub), and have the maintainer use `git merge --squash` > to produce a commit to be pushed to `master`. (Can use a magic commit > message to tell GH that this commit closes the PR.) > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/910dbb5e-f57c-4b81-b093-bfbef6080bbd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
