[Python-Dev] Re: [Python-checkins] CVS: python/nondist/sandbox/Lib README,NONE,1.1 davlib.py,NONE,1.1 httpx.py,NONE,1.1

[Ken Manheimer]

On Tue, 11 Sep 2001, Greg Stein wrote:

> I've now created nondist/sandbox/Lib as a place where people can
> (cooperatively) develop modules intended for inclusion into the core's Lib
> directory. Of course, at your discretion, you can also create
> sandbox/big-project, but the sandbox/Lib directory could be handy for more
> people.

As mostly a bystander in the python development process, i have a question
about an alternative approach.  I believe we (zope dev) use branches for
this kind of thing, and wonder whether you've considered using that? I
gather that this is for things that have not yet gotten approval for
inclusion in the distribution, but that doesn't disqualify the branch
approach - branches need not ever be merged.

The two drawbacks i see with using branches this way:

 - More risk that configuration mistakes can lead to disruption, eg if
   someone thinks they've established their checkout in the branch.

   That said, mistakes using the version control system are generally
   painful, so care is needed in any event.

 - Pollution of the branch namespace.

   This can be mitigated by a good system for choosing names.

The advantage is that the subject files are developed where they're used,
instead of some arbitrary other place.  This is easier on developers, and
means that the initial development history is included in the version
control history, rather than being in some separate (nondist/sandbox/...)
place.

Is it worth considering using branches for this kind of thing?

Ken
klm@zope.com