Ilias Lazaridis wrote: >Chris Forsythe wrote: > > >>Ilias Lazaridis wrote: >> >> >> >>>As the trac team has enouth work to do, I would like to work further on >>>this, taking existent trac-team requirements and tickets in account. >>> >>> >>> >>> >>Since you've made the point that the trac team has enough work to do, >>wouldn't it be better to attach your patches to existing tickets in the >>edgewall trac or submit new tickets with patches attached, since that's >>how the trac team seems to work? >> >> > >please review the thread. > >I've already tried this way, but I cannot wait days - especially when >doing commercial work. > >
The process I indicated does not stop you from working in the your own svn repo on your requirements. However, I'm saying that your proposal to have patches submitted by having trac developers review your codebase and then create the patchfiles from your commits seems kind of a waste. If you know an issue resolves a problem for your customer(s), you could create a patch after the fact rather easily, and then perform the process I described. I just thought it'd be easier on both parties (yours and trac devs), since you'd be able to create specific code in your repo, and generic patches could be submitted to the edgewall trac. If you don't think so, you don't have to do it, but then you are left without a way to trac an issue on the trac devs side. What I mean by this is, the trac devs would have less responsibility to work on issues if they are not in trac. Since you are asking them to proactively look at your svn repo, that takes a lot of extra time and effort on their part with questionable returns. Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
