On Thu, Feb 27, 2020 at 7:20 PM Thomas Passin wrote:
The series starts here:
>
> https://devblogs.microsoft.com/oldnewthing/20180312-00/?p=98215
>
Thanks for the link.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from
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
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
I don't like to fix bugs involving Leo's most crucial code late in a
release cycle. Imo, such bugs should be fixed early in the *next* release
cycle. That way the new can be thoroughly tested.
In the past, I have just postponed work on such issues until an official
release has gone out the
