I would very much like to abandon the 46-maint branch today. Imo, it has caused nothing but grief, with absolutely no benefit.
1. I have had to make lots of changes twice, either by hand or via merges that I never am quite comfortable with. This seems like pure make work to me. 2. Worse, a number of significant improvements, made in the trunk, and later merged into the 46-maint branch, never got acknowledged in the Leo 4.6.3 release notes. This is not entirely the fault of having a separate branch, but having a separate branch didn't help. More generally, it seems to me that long-lived branches are asking for trouble. For example, I recently got bit in the clean-one-node branch by the data reversion bug that was fixed in the trunk weeks ago and released in Leo 4.6.3. Of course, there is no real alternative to the clean-one-node branch: it must exist until we are sure until the trunk has been thoroughly tested with g.unified_nodes = True. Sure, you can say, merge the trunk into the long-lived branches frequently. It's a good rule. But how often do I follow it? :-) Anyway, I am going to abandon the 46-maint branch unless somebody convinces me otherwise. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
