On Wed, 2009-12-09 at 20:25 +0000, Robert Greig wrote: > > I think the safest option is to expose your work through a series of JIRA's. > > If we need to make the code available immediately and/or collaborate > > with others we could create a branch. > > You could work off the branch and then Ted could apply the patches as > > an when they are made available. > > I think this approach - creating patches and applying them to Jira is > very poor for several reasons: > > 1) it is a pain to create patches and attach them to jira (at least I think > so) > 2) it is a pain for a reviewer to extract them from the jira, review and > commit > 3) because of the above it encourages the large code drops that we > have discussed recently
I'd say that using git is pretty good for the purposes of working in the open conveniently but still producing patches attached to jiras. The alternative would be for Ken to work in private producing patches, at the end of the process. Surely working in the open based on the git.apache.org/qpid repo and producing git patches relative to that using git format-patch will ultimately make it very easy for anyone to apply the patches with no ambiguity, and in the meantime allow us to also pull from his work. Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
