> But developers don't commit to the central repository. They commit to > their local "clones" of it, and then at some (much) later stage push > outstanding commits to the central repository. And then there are > feature branches and merges...
Ok. Wrong wording. What I meant was "the time a change was pushed to the central repository by a developer" which is comparable to the pull time from the central repository. > In this case (and usually) it is the other way around: Fixes are done > on master, and those deemed good and important are "cherry-picked" to > a stable branch. (Although technically, as we use different repository > structure for master and 3-4 (single "core" vs. a bunch), it isn't a > cherry-pick.) Excellent. Then all good changes are in the master already :) Thank you for the clarification ;) -- Pedro _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
