2011/8/4 Peter Bonivart <[email protected]>: >> In my experience it's a good idea to make small, effective >> steps. > > I don't think it's efficient when we already see a need to switch to > something else. Also, small things tend to grow which will just delay > the switch.
Yes, I agree that one does works against the other. I'm thinking that the migration to jira will require a large amount of work in one go, which I cannot pull off at the moment. Going down that path is a risk: we might start the work on the migration, and not finish it. This way, we might end up with having spent the time and effort, and getting no bug tracker integration. It's about the risk, and I'm personally inclined going the safer path. I would not mind it if someone else spearheaded the jira migration. The things to do would be: 1. set up an instance of jira, 2. migrate the data (is there a tool for such migration?), 3. tackle the problem of existing links to mantis bugs, they shouldn't return 404 errors, 4. integrate with the buildfarm database. It's probably not a one evening kind of effort. How much time would the migration take, do you think? Maciej _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
