On May 4, 2011, at 2:50 PM, Vincent van Ravesteijn wrote: > Probably not, but I don't understand the problem here. What are these > branches about ?
They are packaging branches. Launchpad (Ubuntu's development website and package management system) provides tools to import code from developer repositories and automate the creation of .deb packages from them. > What are launchpad recipes ? Launchpad recipes describe the process. > How are the branches linked to SVN infrastructure? Bazaar, the distributed version control system that works with Launchpad, is able to import from an SVN repository. It keeps a cache of metadata from that repository which allows it to sort out the centralized commits and merge with the local history. If there is a problem with the meta-data, bzr becomes extremely unhappy and might not allow you to merge new changes. In general, though, it works very well. I've been mirroring the LyX-Devel branch to Launchpad from SVN for nearly a year without any troubles. I've also been able to keep a separate bzr branch with the outline enhancements and ePub work I've done. I'm concerned because the abandonment of SVN will force me to convert those branches. If possible, I would like to see an SVN mirror maintained to avoid that. It would be pretty trivial to push changes from git-master to SVN through git-svn. Depending on which host you select, the process could probably even be automated. Do we have a plan as to what would happen to the SVN infrastructure already in place? Would it be completely abandoned in favor of a git centric solution?
