> Thanks, that's another option to keep in mind. > I hadn't thought about using SVN that way. > Does keeping it all in sync get tricky as the number of different > pylons apps that hook into the template section grows?
Not really. I handle things for it as such: /trunk = active development for future versions /tags/x.y = incremental non-compatible commits /tags/x.yz = incremental backwards compatible commits /tags/-latest-for-release-x.y = "live" tag that gets backward compatible checkins so when we deploy something into an app, we point it towards /tags/- latest-for-release-0.00 -- which will get all updates that are backwards compatible. when we start deviating stuff, then its gets its new x.y tag and live branch. its a little awkward, and i've fucked up a few commits here and there at the beginning, but its pretty --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
