Bastian Doetsch wrote: > Hi, > > as I'm not quite content with how Trac manages our tickets and > Assembla support for Trac is rather limited, I would like to discuss > if we should re-import our trac tickets into Assembla's ticket tool > and use it.
Why not! > Personally, I'd prefer moving to bitbucket completely, but converting > the wiki would probably be too much of a hassle. I was thinking about asking about this about a week ago I have not used bitbucket but it seems like many of you like it a lot, and if so why should we not switch? As I see it the only reason we ended up with assembla back when we moved the stuff from my home computer was that I wanted to keep Trac as I really like it as wiki/bugtracker/changeset viewer and assemble seems like the only good option where we found free hosting combo with trac and hg. But since then others have taken over the "driving force" in the project and my ideas with trac seems like and "old stubborn mans last wish". If you like bitbucket lets at least consider a switch. The nice thing about DVCS is that you can switch code hosting easy and keep all history. The only issues I see with a switch is bringing over some tickets and moving the wiki. The text-part of the wiki is easyly moved. the doc/screenshots are harder but that part desperatly needs reconstructions anyway. So the only problem with switching I see is: - checking the the features are ok (wiki+bugtracking+reposetory permissions) - bringing over tickets. - move wiki (doc page is hard but needs recostructing anyway) - update the link (easy) -- Zingo "Stefan" Andersen (zingo.org and vectrace.com) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MercurialEclipse" 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/mercurialeclipse?hl=en -~----------~----~----~----~------~----~------~--~---
