Hi all, This is a post about the upcoming migration of Magnolia's codebase from Subversion to Git. No panic is to be had, read on for details.
Since about a year, we decided to take the plunge and move to Git. Last December, I started looking into tools to help us migrate to Git. [1] Unfortunately, since then, we've been fairly quiet about it, and I've been so deep into setting up the necessary servers, trying and verifying various migration procedures and planning all sorts of details, that I've even forgotten to talk about it here. So this is it. We're finally moving to Git. Some have been waiting for this for years, and some are probably still a little afraid of this. It's going to be alright. What does it mean to you ? Well, depending on what you do with Magnolia's source, it will mean nothing at all, or perhaps just not much. First off, the existing Subversion (SVN) will remain accessible. Each project which gets migrated to Git will be switched to "read-only", but there are no plans on shutting it down. If you regularly pull sources from our SVN repository, this will continue working, but trunks and branches will not be updated: you will have to clone the new Git repositories instead. Once migrated, the projects will be hosted on the new Git server; it currently has a Gitweb interface, visible at http://git.magnolia-cms.com. Details on how to access and use the new repositories are at http://wiki.magnolia-cms.com/display/DEV/Git+usage. Oh, and another great news: we will also start mirroring our open source repositories to GitHub at https://github.com/Magnolia. We love the GitHub interface, and we suppose you do too. Starting next week (Wednesday April 4th, i.e right after 4.5.2 is released), we will start migrating our codebase to Git. We're currently planning to migrate projects in "chunks", in the following order: * main project (i.e currently at http://svn.magnolia-cms.com/svn/community/magnolia) * ce and ee bundles * all community and enterprise modules * build tools Forge projects will be migrated "on demand": if you have a project on the Magnolia Forge and would like to use our Git repository, let me know ! We are also taking this opportunity to "fix" a little mistake we did recently - it wasn't clear what a Forge module should be, and we started adding some of our own modules to the Forge; this means the CMIS and Device Detection modules will be migrated to the modules/directory of the Git server. Details and reasoning on the wiki. [2] In the meantime, please let me know if you have any concerns or questions, of course. I'll send a pair of other emails before and after migration "chunks". Looking forward for your pull requests ! Cheers, -greg [1] http://dev.magnolia-cms.com/~gjoseph/git-at-magnolia [2] http://wiki.magnolia-cms.com/display/FORGE/Home http://wiki.magnolia-cms.com/display/DEV/Git+usage -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=660fb18b-7193-4571-a823-f3de618b7cad ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
