[Twisted-Python] Twisted Project Jobs Volunteer

[Tim Allen]

On Wed, Nov 09, 2011 at 02:49:50PM -0000, exarkun at twistedmatrix.com wrote:
> On 02:18 pm, screwtape at froup.com wrote:
> >On Wed, Nov 09, 2011 at 01:22:19PM -0000, exarkun at twistedmatrix.com 
> >wrote:
> >>Why do we need to do this again?  There's already
> >><http://svn.twistedmatrix.com/git/Twisted>,
> >><http://svn.twistedmatrix.com/git/Twisted2.git>, and
> >><http://svn.twistedmatrix.com/git/Twisted3.git>.
> >
> >The wiki mentions the first one a couple of times, although strictly
> >speaking you need to add "/.git" to the end to get a URL you can clone
> >from. Apart from being out-of-date, it seems to be missing a lot of
> >branches (there's only 56, and it stopped updating in 2011-03; my
> >personal git-svn hasn't been updated since 2010-09 and has 2062
> >branches), it hasn't correctly imported the branches under "releases",
> >and the only tags are "last_vfs_and_web2" and "releases".
> 
> It's out of date because no one who knows how to keep it updated has 
> taken the necessary steps for that to happen.
> 
> Are there other problems with it which can only be fixed by starting 
> over?

I suspect that the other problems I mentioned can only be fixed by
starting over, yes.

> The point I am trying to convey is that performing some one-off import 
> operation has been done before, repeatedly.  What's going to be 
> different this time that causes the clone to stay up to date?

I fully expect that whatever broke previous attempts will break this new
attempt too. The difference will be that since there's a record of how
the new repository was created, and assuming there'll be a record of
what happened when the new repository broke, this time we'll be able to
reproduce the problem and work out a solution.

> >I guess it's not strictly necessary to have tags or releases imported
> >if the goal is to let people develop patches against trunk, but the
> >fact that branches are missing worries me - if a Twisted committer
> >adds your patch to a branch, you want to be confident that the new
> >branch will actually show up when you update your repository.
> 
> Indeed.  Is this something that's addressed by the git command in your 
> earlier email?

The "--stdlayout" parameter causes git-svn to import branches in the
standard SVN "branches" directory, which is where Twisted seems to keep
its feature branches (the most important ones for people working on
patches).

With some effort it might be possible to import release branches in
"branches/releases", but that's obviously a lesser priority.

> >As for the other two, this is the first I've heard of them. Is there
> >any documentation about how they differ, are there records of how
> >these repositories were created and/or updated that I could add to
> >the GitMirror wiki-page?
> 
> I have no idea where they came from or how they differ.

It turns out Twisted2 is the newest (July 2011) and has about the right
number of branches. It also seems to have imported the various
"ctrl+backslash-2371+2123" branches that I recall causing issues before.
On the other hand, it still imports "branches/releases" as a single
branch, and has no tags. "Twisted3" might have been created for one of
those reasons... or possibly for some other reason that's not
immediately obvious.