On Mon, Sep 7, 2009 at 5:51 PM, Edward K. Ream <[email protected]> wrote:
> But how am I to fix the cache bug in the clean-one-node branch? You don't necessarily need to fix it there, just fix it in 46-maint and merge it to trunk. Though, I assume trunk already has it - I guess we just need to revert to old 46-maint (just before it got "polluted" by merging trunk to it) and start cutting new releases from it. >> I think the best way forward would be to delete the 4.6.3 release and >> release 4.6.4 with quick schedule, based on old 4.6.2. We can cherry >> pick the necessary fixes (installer and cache bug). > > Why not base 4.6.4 on the trunk? Wouldn't that be safer than cherry-picking > bug fixes? No, because trunk has many changes that are not fixes for critical bugs. It's more problematic from version control perspective, but necessary to deliver "safe" code. We can't really rely on trunk before it's had time to stabilize (I rely on it personally, but as we can see others have different experiences). > Where did this come from? I don't recall anything related to leoID in the > 4.6.3 branch? No idea, probably accidental twitch somewhere. Perhaps sys.path cleanup? > Just to double check, is it alright with you to abandon the 46-maint branch? I don't think it's a good idea. I believe we should keep releasing Leo in 2 streams, one with stable bugfix-only stuff and one with new features. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
