@Kevinjohn Gallagher -

Wait, so you’re releasing code that won’t work with the CURRENT version of WordPress?

Yes.

And you’re doing it intentionally to force people who are happy with THEIR platform to use a system YOU want them to use?

No. You're misunderstanding my motivations in releasing code in general, and plugins in specific, I think.

I don't write code for my users, I write code for me. I write code because I'm using it and because I find it interesting.

I'm a coder, therefore I write code.

I release code because the code might help somebody else too, and it's nice to get feedback on ways to improve the code. I'm not all-knowing, and by releasing code and letting other people use and criticize and modify and improve it, I get the benefit of their point of view and their expertise as well. I can use that to create better code for me to use too.

Now, I released SGC because I'd been writing it and using it and many people have asked me for a copy when they saw it live on my site. It's a preview release (0.1), not fully functional or complete. It works with WordPress 3.3 beta 4, because that's what I'm actually running. (I always run trunk, everywhere. IMO, stability is overrated. Most of them I manually update to nightly builds, some I have automatically update via SVN every so often.)

I'm not trying to push an agenda here. if you don't want to use the plugin, then don't. I don't care if anybody at all uses my plugins, because I'm really writing them for me and me alone. The fact that many other people do use and like them is a happy outcome, but not the end-goal. I mean, they're free after all. It's not like they're paying my mortgage.