StatComm: Roadmap

StatComm was launched last Sunday and it is getting 350 downloads in the WordPress Repository just 3 days after launching, I think it is interesting enough for many who want to know a bit about their web statistics. I appreciate those who are taking time for using and testing it.

But this is only the starting point! In this post I present you with a planned roadmap for StatComm.  Currently we are in the first steps and I want to share with you some relevant details about next releases.

StatComm was launched last Sunday and it is getting 350 downloads in the repository just 3 days after launching, I think it is interesting enough for many who want to know a bit about their web statistics. I appreciate those who are taking time for using and testing it.

But this is only the starting point! In this post I present you with a planned roadmap for StatComm.  Currently we are in the first steps and I want to share with you some relevant details about next releases.

Every major release (ex: 1.6 to 1.7) of StatComm will have a different codename, based on the most dangerous actives volcanoes on earth.

Every minor version (ex: 1.6.0 to 1.6.1) will be launched every 1-2 weeks. If neccesary, there will be also emergency fixes which are marked with decimal values (example 1.6.11 will refer emergency fix for 1.6.1 version). Every complete iteration will depend on many considerations based on goals. If the goals are met in the early stages, then I will proceed to the next major version. This is likely to happen in the first one or two iterations(1.6.x or 1.7.x) , but in the following major versions there is planned more complex tasks based on major major features, which maybe will slow the version launching. Stay tuned while the different versions are launched.

Being said that, let’s see the next incoming versions:

1.6.x : Codename: Maun Loa (Hawaii volcano)

Maun Loa Volcano

Goal: code enhancements, conflict resolution & improve and stabilization
Aimed to: New users
In this instance I will focus in stabilization and making a infrastructure to host the following versions. All the modular code will be purged in favor of OOP (Object Oriented Programming), and outdated code will be replaced (example: widgets, outdated fixes, several bugs).The target is to reach a solid code to conform the basis of the following version.

1.7.x: Codename Taal (Phillipines Volcano)

Taal Volcano
Goal: Performance, database optimization, migration path from StatPress outdated versions directly to StatComm.
Users: New users and users who migrates from other StatPress versions.
There are some important concerns in this stage. There will be  a new way to store the data and also a new much improved way to retrieve information.
Those aspects will be covered in this stage. This is also an angular revision, providing assistance to data migration.

1.8.x Codename Ulawun (Papua, New Guinea)

Ulawun

Goal: Graphic Engine, Manage console, enhanced administration.

Potential Users: New and advanced users

This version will be targetting the enhancement of graphics engine, providing flexibility an additional flexible configuration to change the way de data is shown. Another major milestone here.

1.9.x – Codename Nyiragongo (Africa)

Nyiragongo

Goal: New Features, extension widgets, and shortcode. API implementation.

Potential users: New Users & Advanced Users

This stage should be signed by concentration of new features and also flexibility. The target will focus on new features towards widgets, subplugin engine, and aspects to extend the plugin beyond their initial capability.

2.0.x Integration -  Codename  Merapi (Indonesia Volcano)

Merapi Volcano

This implementation would integrate the data collected from the plugin and find the way to merge or combined with other systems and also different other plugins. Initial draft.

2.1.x – Future releases. Codename Galeras (Colombia Volcano)

Galeras Volcano
This future release are almost out of scope right now but many ideas are just on the horizon. Draft in construction.

As you can see, I’ve been trying to draft a previous roadmap since there will be relevant enchancements ahead.Fasten your seatbelt because this ride just started.

Have a nice day!

Every major release (ex: 1.6 to 1.7) of StatComm will have a different codename, based on the most dangerous actives volcanoes on earth.

Every minor version (ex: 1.6.0 to 1.6.1) will be launched every 1-2 weeks. If neccesary, there will be also emergency fixes which are marked with decimal values (example 1.6.11 will refer emergency fix for 1.6.1 version). Every complete iteration will depend on many considerations based on goals. If the goals are met in the early stages, then I will proceed to the next major version. This is likely to happen in the first one or two iterations(1.6.x or 1.7.x) , but in the following major versions there is planned more complex tasks based on major major features, which maybe will slow the version launching. Stay tuned while the different versions are launched.

Being said that, let’s see the next incoming versions:

1.6.x : Codename: Maun Loa (Hawaii volcano)

Maun Loa Volcano

Goal: code enhancements, conflict resolution & improve and stabilization
Aimed to: New users
In this instance I will focus in stabilization and making a infrastructure to host the following versions. All the modular code will be purged in favor of OOP (Object Oriented Programming), and outdated code will be replaced (example: widgets, outdated fixes, several bugs).The target is to reach a solid code to conform the basis of the following version.

1.7.x: Codename Taal (Phillipines Volcano)

Taal Volcano
Goal: Performance, database optimization, migration path from StatPress outdated versions directly to StatComm.
Users: New users and users who migrates from other StatPress versions.
There are some important concerns in this stage. There will be  a new way to store the data and also a new much improved way to retrieve information.
Those aspects will be covered in this stage. This is also an angular revision, providing assistance to data migration.

1.8.x Codename Ulawun (Papua, New Guinea)

Ulawun

Goal: Graphic Engine, Manage console, enhanced administration.

Potential Users: New and advanced users

This version will be targetting the enhancement of graphics engine, providing flexibility an additional flexible configuration to change the way de data is shown. Another major milestone here.

1.9.x – Codename Nyiragongo (Africa)

Nyiragongo

Goal: New Features, extension widgets, and shortcode. API implementation.

Potential users: New Users & Advanced Users

This stage should be signed by concentration of new features and also flexibility. The target will focus on new features towards widgets, subplugin engine, and aspects to extend the plugin beyond their initial capability.

2.0.x Integration -  Codename  Merapi (Indonesia Volcano)

Merapi Volcano

This implementation would integrate the data collected from the plugin and find the way to merge or combined with other systems and also different other plugins. Initial draft.

2.1.x – Future releases. Codename Galeras (Colombia Volcano)

Galeras Volcano
This future release are almost out of scope right now but many ideas are just on the horizon. Draft in construction.

As you can see, I’ve been trying to draft a previous roadmap since there will be relevant enchancements ahead.Fasten your seatbelt because this ride just started.

Have a nice day!

Comments

  1. I’m wating the StatPress migration tool to use this new plugins.
    Thanks guys.

  2. admin says:

    Thanks for your comments. Stay tuned for next versions, there will be an extensive documentation on migration, scheduled for April 2012.

Speak Your Mind

*