Calligra 2.4 Released - Now What?
As the avid readers of Planet KDE and the Dot can hardly have missed, Calligra made its first real release this week. This release has been long in coming - we started the Calligra project almost one and a half years ago, which is a long time for free software. But the release made the wait worth it: Two new applications, a completely rewritten text layout engine that doesn't prevent showing of any feature in ODF, improved filters, etc, etc. Not bad...
And most important of all: This release is the foundation of the things to come. We took a long time to get it out because we wanted the foundation to be strong enough so that we can build a sky scraper on top of it. From now on we will release new versions every 4 months and make the process more incremental.
We will do this by adopting a stricter policy for committing into the master branch so that in principle it stays releasable all the time. The basic rules will most likely look like this. Allowed into master are:
So that brings us to the question in the title: Which features are most important to implement in the UI at this point? Also, which bugs are the most irritating for you? Let us know through bugs and wishes at http://bugs.kde.org/ ! You can find all the Calligra applications as calligrasomething where something is the name of the application.
You can of course also write comments to this blog entry but it is not guaranteed that the team will read them.
One thing that we already know will be part of 2.5 is improved manipulation of text tables since boemann, the Calligra Words maintainer, blogged about it. Of course I have my own pet list of things to improve but that's not the point of this post so I won't list it here.
And most important of all: This release is the foundation of the things to come. We took a long time to get it out because we wanted the foundation to be strong enough so that we can build a sky scraper on top of it. From now on we will release new versions every 4 months and make the process more incremental.
We will do this by adopting a stricter policy for committing into the master branch so that in principle it stays releasable all the time. The basic rules will most likely look like this. Allowed into master are:
- single commit bug fixes
- merges from feature branches or single commit features
So that brings us to the question in the title: Which features are most important to implement in the UI at this point? Also, which bugs are the most irritating for you? Let us know through bugs and wishes at http://bugs.kde.org/ ! You can find all the Calligra applications as calligrasomething where something is the name of the application.
You can of course also write comments to this blog entry but it is not guaranteed that the team will read them.
One thing that we already know will be part of 2.5 is improved manipulation of text tables since boemann, the Calligra Words maintainer, blogged about it. Of course I have my own pet list of things to improve but that's not the point of this post so I won't list it here.
Labels: calligra
posted by ingwa at 8:41 AM
5 comments
