On 12/11/05, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > Fredrik Lundh wrote: [SNIP] > > - I check in an existing elementtree release in a separate location in > > the svn.python.org source tree. e.g. > > > > svn.python.org/kits/elementtree-1.2.6-20050316 > > > > this will make it clear that this is external software, and it also > > provides a reference point for tracking down local changes > > Ah, so you want what CVS calls a "vendor branch": code that is > externally maintained, and imported from time to time. > > Clearly, "local" (i.e. python.org) changes are one primary issue, > so we should agree on an update process - I would personally prefer > one that allows for merging (in the "svn merge" sense). > > The other issue is, of course, the question whose job it is to actually > perform the updates. Would you expect to do that yourself, or would > you expect somebody else does that? >
I remember Barry saying he wanted to start a branch for work on the next version of the 'email' package. And it is possible more and more modules developed externally will begin to be included in the stdlib. Perhaps PEP 2 should be updated with basic guidelines we plan to stick to for modules that are externally developed and occasionally synched with the core. Basically I think specifying who the code comes from, having auto-assignment for bug reports in the tracker, and saying that no updates to the snapshot except for bug fixes once alpha is released should be enough. I would assume the snapshot in svn would just be a direct copy to the core and not require running any special script or something to generate anything. If we do go that way, then mentioning that in the PEP wouldn't hurt either. -Brett _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
