Yes, and some would say that you should open a separate new branch for every single bug. If you haven't seen it, Raymond Chen's The Old New Thing had a whole series on how to organize, merge, and commit git branches to avoid strange problems like giving the "blame" to the wrong person. Very worth reading if you haven't encountered the series yet. (What he's dealing with is way beyond anything I've had to deal with, but you are working on a much larger code base with many more contributors than I).
The series starts here: https://devblogs.microsoft.com/oldnewthing/20180312-00/?p=98215 On Thursday, February 27, 2020 at 12:13:36 PM UTC-5, Edward K. Ream wrote: > > On Thursday, February 27, 2020 at 10:41:03 AM UTC-6, Edward K. Ream wrote: > > At last I see that I can begin work on a potentially dangerous issue *now, >> *even if it is prudent to include the issue in some later release. This >> allows important bug fixes to be tested immediately. >> > > Some additional thoughts: > > 1. This work flow reduces the coupling between issues and releases. > > The only constraint is that significant fixes should be merged into devel > early in a release cycle. > > 2. This work flow privileges those who use Leo's github repo. > > Imo, that's exactly as it should be. Yes, there is value in having > official releases, but those releases should not impair development in any > significant way. And now they don't :-) > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/00b5f2b3-5749-4164-84f7-8b9da5c47d8f%40googlegroups.com.
