> > FWIW Jira seems to be an exception among bug trackers: some people really > love it, others really hate it. It depends on who set it up and maintained > it in the company where they used it. > > Since we don’t have a resident Jira expert, we run the risk that most of > the Django community will fall into the “hate it” bucket. To me this is one > of the riskier choices we could make. > > Anyway it’s unclear to me that the potential benefits of switching to any > bug tracker could offset the transition costs, as long as Trac is > serviceable. > > We’ll see what happens in 2020 if it doesn’t support Python 3 by then ( > http://trac.edgewall.org/ticket/10083, > http://trac.edgewall.org/ticket/12130). >
Could always look at Bloodhound (http://bloodhound.apache.org/) if after something similar. Not that it supports Py3 yet. But I'm with everyone else. It's not worth it. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAGuvt93%2BabKpnA%2BFC2Ny5HYn3p_8mdS_%2BrPV3jg3NFoV%3DgHvyw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
