After a couple of late nights reloading repository dumps and learning new and wonderful unexpected “features” of mixing svn:externals and svnsync, I’m happy to announce that publicsvn.songbirdnest.com is finally available again.

Timelines are back up as well.

All external developers will need to repull their trees; these repositories—multiple—are entirely new SVN repos, with different UUIDs. Some Subversion clients will ignore this (minor?) detail, and you can still update repos, but it’s likely to cause grief later.

Also, the repository paths have changed; please see our developer documentation on Checking out the Code for details on the changes and to figure out what you will want to repull.

We apologize for the inconvenience caused by having to repull trees, but we were long due for a repository reorganization.

An overview of some of the changes:

• Different kinds of code are split out into different repositories
• Branching and tagging will now follow standard Subversion practice, i.e. no more $tagName/trunk directories.
• Brand new, faster publicsvn server (thanks Tyler!)
• https is no longer supported on publicsvn, since it’s not necessary. This reduces load on the server, meaning faster pulls for you!
• Backups are more manageable; backups of our main repository now take five minutes instead of three hours; restores take twenty minutes instead of twelve hours); this means other processes, like mirroring changesets to publicsvn, is faster!
• We’ve pruned code that wasn’t necessary for a standard Songbird build, meaning faster pull and update times!

Thanks to everyone for being patient while we worked all the details out, and thank you to Mitch on IRC, whose pestering kept me honest while we did this; I needed it.