Skip to content

Changes to the Release Cycle

I’ve decided to change the way I do releases.  In the past, I’ve typically done two types of releases, Bug fix releases, and Major releases.

The major releases where quite large, sometimes 40 to 50 different tickets.  Major release version numbers were two digits like 1.0, 2.4, etc.

The bug fix releases where smaller, usually just 2-5 tickets, and the version numbers where three digits, like 1.0.1, 2.4.1, etc.

The Old Way

One of the biggest reasons for this type of versioning/release management is that any theme or plugin that works on 2.4, should work for all 2.4.x versions. This makes it easier on the users, to tell which theme/plugin works for what.  And also is less updating for site owners.

The problems with however are, it takes forever between releases, so users have to wait a long time for new updates.  And it also makes development harder, trying to keep track of so many tickets per release.  This leads to more bugs.

The New Way

Going forward however, I will be doing small releases.  This will allow for much faster development of new features, and will eliminate the need for three digit version numbers.  The new releases will contain no more than 10 tickets and will probably be more like 3-5 tickets.

The biggest downside to this is the frequent upgrades users will have to perform.  The solution to that is that 2.5 will contain a automatic upgrade system, which will hopefully eliminate most of the current issues with upgrading.

FCMS 2.5

The next version will contain just the Status Updates feature and the Automatic Upgrade feature.  The Video section will have to wait for the 2.6 release.

Be Sociable, Share!

Categories: News.

Comment Feed

4 Responses

  1. Great idea !
    I use frequently the automatic upgrade of WordPress and it’s a great feature.
    I will be a great fan of the 2.5 release then !

  2. Can i have facebook, twitter social media plugins for the new version? whats the approximate date of 2.5 release.?

  3. There will be some facebook/twitter integration in the 2.5 release.

    And I am planning on having it done by the end of the month.

  4. Great news a new user, and looking forward to being a longtime user :)

Some HTML is OK

or, reply to this post via trackback.