Pentaho Reporting version will be 5.0, in sync with BA-Server

It is now official. The next release of Pentaho Reporting will be numbered 5.0, in sync with the Pentaho Suite 5.0. Future releases will then keep in sync with the suite version number and will be released at the same time as the Pentaho Server.

Although it is a shame that you will no longer be able to impress friends and family with the arcane knowledge of what PRD goes with a given release of the BA-Server, it will simplify the story for support, marketing, sales and everyone else.

We are now also officially in feature-lock-down. We thus have finally entered the last stages of the development process (the remaining phases being ‘stress’, ‘panic’ and ‘outright agony’). That means, no new features get added, regardless how good they are, and we now concentrate solely on working though the remaining items of the sprint backlogs.

Related posts:

  1. PRD-3639: On Adding Version checks into Pentaho Reporting
  2. Launching the Pentaho Reporting status portal and version 3.6.1 available
  3. How to upgrade your old BI-Server to Pentaho Reporting 3.7.0
This entry was posted in Announcements on by .
Thomas

About Thomas

After working as all-hands guy and lead developer on Pentaho Reporting for over an decade, I have learned a thing or two about report generation, layouting and general BI practices. I have witnessed the remarkable growth of Pentaho Reporting from a small niche product to a enterprise class Business Intelligence product. This blog documents my own perspective on Pentaho Reporting's development process and our our steps towards upcoming releases.

7 thoughts on “Pentaho Reporting version will be 5.0, in sync with BA-Server”

  4. ThomasThomas Post author

    We are currently in the last moves of building the final build. At that point, traditionally our development work is done, but it will take another 3 to 4 weeks to actually get the builds out to Sourceforge.

    (I know, how hard can it be to upload that. But a release is more than just dropping software in a folder – marketing, training, support, all of them need to be updated and in in sync. Even when engineering no longer changes the release, other parts of the organization are frantically working to get their share out. (And probably cursing all engineers for making last minute changes and bugfixes 🙂 ) )

Comments are closed.