Luke Plant wrote: > >> b) create a permanent branch "patch" (or a seperate svn) where commit >> access is granted essentially on request. >> >> c) the remaining patches can be applied by the contributers to the >> "patch" branch. >> >> the patch committers can collaborate to keep the branch stable >> >> the core committers make the verification / merge of files/subsystems on >> request. >> >> Users can decide which patches to retrieve, by just merging from the >> patch branch. > > Unfortunately, having this as a svn branch is just not practical -- the > cost of maintaining a branch like this, which tracks trunk but just > goes on indefinitely, is way too large. You would have to use a > different VCS system, with better support for merging and cherry > picking and things like that, and then merging into the subversion > trunk would still be a pain.
I understand. > I'm not sure this proposal addresses the core problems i.e. 1) getting > some timely feedback about whether a patch is likely to be accepted 2) > actually getting the patches into trunk in a timely manner. You are right, my proposal addresses to avoid patches at all, as it is an inconvenient way to contribute. > I'll try to post some of my own thoughts soon. > > Luke > > > > > -- http://lazaridis.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers -~----------~----~----~----~------~----~------~--~---
