> I've svnsynced the SVN repo so that we can work on it efficiently, and
> I've already talked with Augie Fackler, the hgsubversion maintainer,
> about what the best way forward is. For example, we may want to leave
> some of the very old history behind, or prune some old branches.
I'm -1 on removing very old history; it's still useful to find out
that some change goes back to 1994. I'm -0 on removing old branches
(your 18 month policy sounds reasonable).
>> - Convert the current svn commit hooks to Mercurial.
>
> Some new hooks should also be discussed. For example, Mozilla uses a
> single-head hook, to prevent people from pushing multiple heads. They
> also have a pushlog extension that keeps a SQLite database of what
> people pushed. This is particularly useful for linearizing history,
> which is required for integration with buildbot infrastructure.
FYI: this is the list of hooks currently employed:
- pre: check whitespace
- post: mail python-checkins
inform regular buildbot
inform community buildbot
trigger website rebuild if a PEP was modified
(but then, whether or not the PEPs will be maintained
in hg also needs to be decided)
>> - Augment code.python.org infrastructure to support the creation of
>> developer accounts.
>
> Developers already have accounts, don't they?
Depends on the term "account". There is a mapping ssh-key <-> logname.
> In any case, some web
> interface to facilitate setting up new clones (branches) is also
> something that's probably desirable. I think Mozilla has some tooling
> for that which we might be able to start off of.
How to authenticate in that interface? We don't have passwords per
committer.
Regards,
Martin
_______________________________________________
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
