{"thread":{"id":"55088","subject":"RFC -- making a plan for remainder of merge-ort","startedAt":"2021-02-02T03:53:05Z","lastAt":"2021-02-03T05:49:07Z","messageCount":3,"participants":["Elijah Newren","Derrick Stolee"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"415878","messageId":"CABPp-BHvk5RLq3OOYhcQZJ_9w6hbQUVurJiRrks8kcGq5-rn0g@mail.gmail.com","threadId":"55088","inReplyTo":null,"subject":"RFC -- making a plan for remainder of merge-ort","fromName":"Elijah Newren","fromEmail":"newren@gmail.com","sentAt":"2021-02-02T03:52:04Z","receivedAt":"2021-02-02T03:53:05Z","isPatch":false,"sender":{"key":"newren@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5455730?v=4"},"body":"Hi everyone,\n\nThere will be ~11 more series (with about ~6-7 patches per series)\nbefore merge-ort is complete.  Now that gitster/en/merge-ort-perf has\nmerged to next, I can start submitting the next series.  Some\nquestions before I do so, though:\n\n* What's the right rate to submit them to not overwhelm reviewers? One\nper week?  I didn't get much feedback on this for the past series.\n[One per week, assuming the git-2.32 cycle is 3 months long, would\nmean finishing in about 3 months, i.e. just a few weeks before\ngit-2.32-rc0.]\n\n* My focus for the next few series is on diffcore-rename.c, which will\nalso affect things other than merge-ort.  While each series is\nself-contained, given that 2.31-rc0 is just over 3 weeks away I'm\nwondering if it makes sense to hold my future diffcore-rename series\nout of 2.31 and start merging them in the 2.32 cycle.  Thoughts?\n\n\nThanks,\nElijah\n"},{"id":"415916","messageId":"bae3726e-25e1-90e5-b0e3-5c2d0c4cd26a@gmail.com","threadId":"55088","inReplyTo":"CABPp-BHvk5RLq3OOYhcQZJ_9w6hbQUVurJiRrks8kcGq5-rn0g@mail.gmail.com","subject":"Re: RFC -- making a plan for remainder of merge-ort","fromName":"Derrick Stolee","fromEmail":"stolee@gmail.com","sentAt":"2021-02-02T11:33:00Z","receivedAt":"2021-02-02T11:35:58Z","isPatch":false,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"On 2/1/2021 10:52 PM, Elijah Newren wrote:\n> Hi everyone,\n> \n> There will be ~11 more series (with about ~6-7 patches per series)\n> before merge-ort is complete.  Now that gitster/en/merge-ort-perf has\n> merged to next, I can start submitting the next series.  Some\n> questions before I do so, though:\n> > * What's the right rate to submit them to not overwhelm reviewers? One\n> per week?  I didn't get much feedback on this for the past series.\n> [One per week, assuming the git-2.32 cycle is 3 months long, would\n> mean finishing in about 3 months, i.e. just a few weeks before\n> git-2.32-rc0.]\n\nI promise to get back to reviewing with a faster turnaround soon.\n\nIf these are smaller series (and ~6-7 patches per would be smaller)\nthen I could see most of them stabilizing within a week. I think the\nbiggest thing for dependent series is to allow one to stabilize\nbefore starting the next one. OF course, we can _think_ something is\nstable and then a contributor appears with insightful comments a week\nor more later.\n\n> * My focus for the next few series is on diffcore-rename.c, which will\n> also affect things other than merge-ort.  While each series is\n> self-contained, given that 2.31-rc0 is just over 3 weeks away I'm\n> wondering if it makes sense to hold my future diffcore-rename series\n> out of 2.31 and start merging them in the 2.32 cycle.  Thoughts?\n\nIt might be fine to get the code under review, but ask Junio to\ndelay merging into 'master' until shortly after release. This\nensures that there is plenty of time to \"simmer in CI.\"\n\nThanks,\n-Stolee\n"},{"id":"416030","messageId":"CABPp-BHqk3UkauL-MmQ+JBJvhC6WRhJJM+yLvXiENZNn+CTw5w@mail.gmail.com","threadId":"55088","inReplyTo":"bae3726e-25e1-90e5-b0e3-5c2d0c4cd26a@gmail.com","subject":"Re: RFC -- making a plan for remainder of merge-ort","fromName":"Elijah Newren","fromEmail":"newren@gmail.com","sentAt":"2021-02-03T05:48:13Z","receivedAt":"2021-02-03T05:49:07Z","isPatch":false,"sender":{"key":"newren@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5455730?v=4"},"body":"On Tue, Feb 2, 2021 at 3:33 AM Derrick Stolee <stolee@gmail.com> wrote:\n>\n> On 2/1/2021 10:52 PM, Elijah Newren wrote:\n> > Hi everyone,\n> >\n> > There will be ~11 more series (with about ~6-7 patches per series)\n> > before merge-ort is complete.  Now that gitster/en/merge-ort-perf has\n> > merged to next, I can start submitting the next series.  Some\n> > questions before I do so, though:\n> > > * What's the right rate to submit them to not overwhelm reviewers? One\n> > per week?  I didn't get much feedback on this for the past series.\n> > [One per week, assuming the git-2.32 cycle is 3 months long, would\n> > mean finishing in about 3 months, i.e. just a few weeks before\n> > git-2.32-rc0.]\n>\n> I promise to get back to reviewing with a faster turnaround soon.\n>\n> If these are smaller series (and ~6-7 patches per would be smaller)\n> then I could see most of them stabilizing within a week. I think the\n> biggest thing for dependent series is to allow one to stabilize\n> before starting the next one. OF course, we can _think_ something is\n> stable and then a contributor appears with insightful comments a week\n> or more later.\n\nYeah, smaller on average, but there is a long one early on.  The next\neight series' patch counts are: 2, 3, 11, 7, 8, 7, 6, 7.  I don't have\nones beyond that ready quite yet.\n\nAlso, for the next nine series, each one will depend upon the previous one.\n\n> > * My focus for the next few series is on diffcore-rename.c, which will\n> > also affect things other than merge-ort.  While each series is\n> > self-contained, given that 2.31-rc0 is just over 3 weeks away I'm\n> > wondering if it makes sense to hold my future diffcore-rename series\n> > out of 2.31 and start merging them in the 2.32 cycle.  Thoughts?\n>\n> It might be fine to get the code under review, but ask Junio to\n> delay merging into 'master' until shortly after release. This\n> ensures that there is plenty of time to \"simmer in CI.\"\n\nMakes sense; I'll submit the first one.\n"}]}