Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index 

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

Context

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.