EllisLab today announces changes to our internal development processes, including dropping Subversion in favor of Mercurial and adopting Assembla as our agile software development management tool.  Along with these changes, CodeIgniter 2.0 pre-release code is in development, and is now hosted at the Mercurial-focused social coding site BitBucket.

Read the full details at CodeIgniter.com.

I was reading the article but had to stop after ‘not git’; my vision went all red and hazy and I came to standing over a dead caribou in northern Canada. /facetious

Good news!

but I dont understand why not GIT and GITHUB?

MpaK - 11 March 2010 06:18 PM

but I dont understand why not GIT and GITHUB?

Welcome to our community, we’re thrilled to have you!

From the article

We looked at Git first, whose growth can be largely attributed to the popularity of GitHub, then Bazaar, darcs, Monotone, Perforce, BitKeeper, and so on.  But after weeks of research and test use, we settled comfortably into Mercurial.

Now before the Git readers get their pitchforks ready and head for the comments, let me be clear that we are not at odds…

... and it goes on. So I think you are asking for something more specific then this? Do you want to elaborate?

And just so that we’re 100% clear - WE LIKE GIT. A lot. Git is brilliant, in many of the same ways mercurial is brilliant. This is not an anti-Git decision, but rather a pro-mercurial decision.

All looks good, glad to see things progressing as it has felt a little stale around here for some time while the EE 2.0 stuff was going on, so looking forward to the various new functionality that CI 2.0 will bring!

Looking forward to the new code. A quick browse has me very excited about 2 things in particular:

1) getting rid of plugins. The distinction was never very clear and I think this move will help clear things up for newer users.
2) Packages. Getting ready to download and play with the latest code, but I think the addition of a built-in module system will help the community grow even more.

Thanks so much for all of your hard work. I’m not sure if you have any idea just how much your community appreciates it.

ok, if you like Mercurial I will like it too ))

Did you CodeIgniter 2 some roadmap? All what I saw in bitbucket is CI 1.7.2 with some changes in files structure: “codeigniter” renamed to “core”, some javascript and jquery libraries, some configs and nothing so global what need to all: extensible ORM, NoSQL drivers (Mongo, Redis), Modular (like HMVC), flexible Cache system? What we will see in new CI?

(sorry for my english ))

Look for news on CI 2.0’s future in the coming weeks, MpaK.  The code you see now is just the start.

Moving to Mercurial and bitbucket was a wise choice imho, good job

I have also used Assembla in the past and GitHub, CodaSet or similar sites can’t really compare to it.

Assembla offers you almost any kind of feature you can think off (including automatic building and continuous integration, etc.)

Generally I like improvements, but let me explain you some problem your choices made for me :

1. I have about 30 websites wich download Codeigniter from the SVN repository using SVN externals so I get the freshest version all time. Now I have to change the settings on all of them.
2. That’s the most annoying one: My editor which is CODA from Panic doesn’t support Mercurial. That sucks.

Can’t you set back your SVN repo and duplicate the Mercurial commited code to it periodically so I can continue to work with my favourite tools ? (yeah I don’t want change my editor)

Awesome! I did a quick run-down of the things I noticed in the new CodeIgniter 2.0 source.

Too Pixel - 11 March 2010 08:33 PM

Generally I like improvements, but let me explain you some problem your choices made for me :

1. I have about 30 websites wich download Codeigniter from the SVN repository using SVN externals so I get the freshest version all time. Now I have to change the settings on all of them.
2. That’s the most annoying one: My editor which is CODA from Panic doesn’t support Mercurial. That sucks.

Can’t you set back your SVN repo and duplicate the Mercurial commited code to it periodically so I can continue to work with my favourite tools ? (yeah I don’t want change my editor)

I complete agree! I’m using Versions (SVN Mac Client) and now anytime I open it, I’m getting killed with tons of requests for authentication to the SVN repo!

Sorry guys, we won’t be maintaining a Subversion mirror server, we’re done with svn.  You are certainly free to use a bridge and maintain your own Subversion repositories of the source code, though.  You may also find these Hg resources handy.  It really is a joy to work with in comparison, even if you end up embracing the command line.

Mercurial: The Definitive Guide
Hg Tips
Hg Init: a Mercurial tutorial by Joel Spolsky
Hg Cheatsheet
Hg Guide - goes through use case workflows from the simplest (non-code log keeping) to complex (collaborate feature development).
hgrc config files - additional reading on the many things you can do with Hg config files.
Murky, a GUI that lets you visualize and manage repositories and source files without using the command line.

  TextMate Mercurial Bundle - installation instructions:

  Then in TextMate, select Bundles > Bundle Editor > Reload Bundles.
 
  Now when you have a project open in TextMate that is under Hg source control, you can interact with the repository via CTRL+SHIFT+M, or via the bundle command menu if you prefer to use the mouse.

I’m glad to see you guys decided to ditch Subversion, it’s about time. :D

At the same time I wish you preferred Git. I don’t have anything against using Mercurial, but the fact that GitHub has provided developers such an AWESOME ecosystem… I know from my personal experience, I wouldn’t have contributed to some of the open source projects if it wasn’t for the fact that GitHub is so easy for forking projects and has an astonishing number of developers and development groups.

Any road maps for the 2.0 branch?

Derek, I didn’t said you have to maintain a SVN repo eternally, but you could at least have made an announcement some weeks ago with a deadline date to let people switch slowly, now when I open CODA I have 30 websites messed up which was not an attended work for me today + CODA does not yet have a plugin or extension to support Mercurial (Yeah, not everybody is using Textmate…).

[Mod Edit: Watch the language, please.  Thanks.]

Well, as I mentioned, we couldn’t have anticipated that anyone would have tied their sites so closely to our subversion server.  I’ve reopened read access for you and will leave it open for a week or so.  It is not mirrored, so it does not have CodeIgniter 2.0.