Plugin refactoring
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
Beginning today (well in a bit, I’m on a quick coffee break) I will be performing a complete audit on all of our property related plugin code (enquiries, bookings and property manager) and also moving everything from Google Code across to it’s new home at Assembla.
Since starting developing these plugins, I have increased their scope and functionality to the point, now, where they have started to overlap in more and more complex ways (development versions). Whilst this is fine, to a point, for a single person to maintain, I have increasingly found myself spending longer trying to work out where a particular bit of functionality should belong. So I dread to think what trouble there will be with more than one person to maintain the code base.
What does this mean?
As I don’t currently know of anyone who downloads the plugins using SVN, it will mean very little to everyone out there. Downloads of the existing versions will still function as before. The code held in the Google code SVN will be frozen as of today.
For myself, and the new team, it provides us with a lot of new toys such as an integrated Trac system, ticketing and project management. Which will, hopefully, mean the new development will move forward quicker and in a more structured fashion than my current “code when I have time” development method.
More announcements coming soon.
Tags: google code, plugin, property, svn, trac, wordpress