I never dreamed that bzr would make such a difference to the Leo project. The energy level and the level of collaboration are both markedly greater today than they were a week ago. We now have a true partnership of developers. This has been one of my dreams for Leo.
The more I play with branches and merges, the more opportunities I see. For instance, as we get closer to an official release, I can create a branch for the release that only I can push to. There is no great need to be careful with the trunk. Indeed, the question of when to merge doesn't seem all that important. You can merge whenever you want. It's no big deal if sources get temporarily out of synch: another merge is usually all that is needed. Edward P.S. My present preference is not to create branches for small changes like bug fixes, but perhaps that is only because I usually am the one fixing bugs. A branch for the new Vim plugin, for example, seems reasonable: it is a snapshot of an improvement. It's self contained, and can easily be diffed against other branches. EKR --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
