[Buildbot-devel] Buildbot is switching to Git, dropping CVS mirror?

[Brian Warner]

So, Dustin has talked me into switching the Buildbot source code from
Darcs over to Git. I don't have any experience with Git yet, so this
will be a learning opportunity :). We haven't figured out how the
repositories will be set up, but my plan is to have a canonical one on
buildbot.net just like the old darcs repo. Other developers will have
trees in other places, of course, but we'll do the releases off the
buildbot.net tree. So tickets need to remain open until their associated
changes have been pushed into the trunk branch on the buildbot.net repo.

If I can figure out how, I intend to maintain a darcs mirror (read-only)
in its current location on buildbot.net .

Would anyone mind if we were to drop the readonly anonymous-CVS mirror
that lives on sourceforge? I'm not sure the scripts that keep it
up-to-date are even still working.. I keep seeing ssh permissions
problems when I push changes into the darcs repo.

With Git (as opposed to Darcs), we should be able to have easier
feature-branches (since Git can do in-repo branches, without additional
hosting/mirroring support necessary for each branch). So, e.g. the
SQL-based status work can take place on a separate branch, but still be
copied all of our trees at the same time as other patches.

We still have some workflow questions to sort out, as we gain experience
with the new system. But I expect that this will make it easier to get
more people involved in Buildbot development, which should help us get
those OnePointOh features in place sooner.

cheers,
 -Brian