On 15/05/2018 17:07, Volker Braun wrote:
The integration branch is going to have its history rewritten regularly.
Why is that? Shouldn't the process be simply 1. create a branch TMP = "integration branch" + "merged positive review ticket" 2. if merge fails: move back ticket to needs work and go back to 1 3. if any test fails: move back ticket to needs work and go back to 1 4. set the integration branch to TMP and go back to 1
The issue is that unsuspecting developers might *base* their contribution on the integration branch (i.e. go to github and select the branch with the most recent commits), and then have it yanked out from under their feet when I rewrite it.
This would indeed be terrible. But to my mind, this should not happen. Best Vincent -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
