[Development] Proposal: New branch model
Jedrzej Nowacki
Jedrzej.Nowacki at qt.io
Thu Jan 24 11:47:34 CET 2019
Dnia środa, 23 stycznia 2019 17:37:57 CET Konstantin Tokarev pisze:
> Note that backporting changes from dev should also be a full-time job for
> someone, otherwise amount of fixes going to stable branches will likely
> drop
Yes, depending who you ask it is good or bad. It means that only fixes that
someone really cares about are really integrated to the stable branches. If
somebody cares about a fix it means that it is more important. More over
cherry-pick mode distributes the load of conflict resolution.
> > - there is a chance, that some cherry-picked commits may be left
> > forgotten in gerrit after a failed integration
>
> Or not submitted at all because of failed cherry-pick. Also, notorious
> property of cherry-pick strategy is explosion of conflicts: if there is a
> patch series modifying some code, and first of them requires adjustment to
> resolve conflict, it's likely that all fol
> lowing patches will have
> conflicts as well in the same places.
Assumption is that a bot would do the cherry-picking for you. If a cherry-pick
cause conflicts, then the bot would push unresolved conflict to gerrit. So no,
all changes would be in gerrit. Some may be to hard to resolve or one would
lack a motivation. Again, main point is that it is up to author to resolve the
conflicts.
Cheers,
Jędrek
More information about the Development
mailing list