On Sat, Mar 22, 2008 at 8:59 AM, Tobias Bocanegra <[EMAIL PROTECTED]> wrote: > > > My work practice will be to take a branch of Commons CLI using either > > > Bazaar or Git -- I don't think Mercurial has proper Subversion support > > > as yet, so is not an option. This will almost certainly be a branch > > > without previous history to avoid having to process 639959 commits! I > > > will then keep a Subversion Head mirror and a personal branch of > changes > > > to create patches. I would publish these branches and cross merge with > > > anyone else actively working on this. So this solves the problem of > > > needing Subversion commit access to progress. However, it does require > > > someone with commit access to triage and process patches on an active > > > basis. > > > > As long as it ends up being atomic patches in the JIRA; any work > > practice is great :) > i'd be happy to work on the issues as well. since i don't have the > proper JIRA karma to accept issues, how should we coordinate issue > resolving?
Generally you just comment and attach patches; then when the patch is applied the issue is closed. The assign and resolve features are rarely used. If you're working on a feature, just say so in the comment. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
