> I'm not 100% sure I follow you here. What is your suggestion? I > think it makes sense to maintain a svn repository that has reasonably > current code for several months at least. The question is how often > to merge changes over to that repository, and how fine-grained the > history of that repository needs to be. Would it be good enough to > just do a svn checkin nightly from the current mercurial tip? -- > perferably only if all the tests pass. ;) > > Or should we try to automate it so every changeset is pushed over > separately?
If I were the user in question, I would not find it all unreasonable to have daily snapshots, and would probably prefer daily passing snaps. After all, if I *need* bleeding edge, I can get it via hg and merge myself. > Yea, we should definitely document how the conversion is done, and how > people can move their TG related projects to our new hg+trac system > when they want to make that change. A big +1 on that. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
