Just a thought on your comment on making things easy for the contributors: Maybe it's better to make things easier for the committers? I've been following this list for a couple of months, and it seems to be a reoccuring issue that patches are available but it takes a (more or less) long time before they are applied.
Speeding up the release cycle would be more interesting from my point of view! Unfortunately I haven't got a solution for the issue... /Johan 2007/11/12, Jason van Zyl <[EMAIL PROTECTED]>: > > On 12 Nov 07, at 7:50 AM 12 Nov 07, Jochen Wiedmann wrote: > > > On Nov 12, 2007 1:40 PM, Brett Porter <[EMAIL PROTECTED]> wrote: > > > >> I might be misunderstanding, but this sounds like the answer to my > >> other question about getting contributors changes into trunk - what I > >> was asking here is how after someone has merged the changes, we can > >> keep track of where they came from (relying on an external repo url > >> is not realistic for this, in case it goes away in the future). > >> > >> Aside from that, do you have a guess at how long this takes/easy it > >> is to do? I may be missing something, but it sounds worse than > >> applying a patch from JIRA :) > > > > It's easier for the contributors which is the point. At least the ones > who want to use version control while they are working. People can > still submit patches. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
