OpenLP 2.0.4 has been out for 4 months now, and while there don't seem to be any major issues with it, that doesn't mean there are no more bugs. With this in mind we're going to be releasing version 2.0.5 at the end of this month, June. This will be the last release of OpenLP 2.0.
Once 2.0.5 has be released, we will be gearing up for the release of 2.2. As a part of this we will be starting up the nightly builds again and we will release a beta at the end of August with a view of releasing 2.2 at the end of October.
In order to reduce the time between (major) releases, the OpenLP team has decided to move to a release cycle more like Firefox and Chrome, with short cycles and a smaller number of features in each release. With fewer features in each release there should also be fewer bugs, and a faster cycle should mean that bugs are fixed sooner too.
We have also started writing automated tests for OpenLP, which should help to curb some of the bugs before they make it into our main codebase. Each developer is required to run all the tests against their code before they can submit it, and they are required to write tests for their code. This way our test coverage increases and we are able to prevent regressions (when new code breaks some of the older code).
So while you won't find all the features you want in OpenLP 2.2, we hope to be able to get the features you want out to you sooner in future because we're not spending forever getting all the features developed while you're waiting for a huge release to happen.
Recently, Raoul (the project leader) was interviewed by church media expert Chip Dizárd about OpenLP and open source software on his Amazing People Podcast series. If you'd like to hear Raoul's take on OpenLP, open source and the church, then don't hesitate to listen to the podcast.
Update: We are pleased to announce that we've had another large donation, which will cover the cost of the Mac Mini completely. Thanks very much for the generous donations! If you would still like to donate (it would be nice to get a Mac keyboard too), we're still accepting donations.
As awesome as OpenLP is, we do have a rather large weak point: Our Mac support. Presentation software integration doesn't work on Mac OS X, there are often multiple display issues, and we don't have a dedicated Apple/Mac developer.
The good news is that we've recently been given a large donation toward purchasing a Mac Mini. The bad news is that it isn't enough. We need another USD$150.
If you're interested in donating towards buying a Mac Mini, please contact us via support<at>openlp.org or come visit us in IRC and ask for the PayPal details.
Welcome to another bugfix release of OpenLP 2.0. This is a further release in the stable 2.0 series. While it might not look like much, we're hoping that this release will make everyone's lives just a little bit easier.
Bugs fixed in this release:
#1117098: Transparent theme is white on Mac OSX
#1154467: Web download bible db's getting locked
#1173749: Songs with mismatching formatting tags still throw an exception
#1252477: Changing theme on bible settings tab causes an error when saving service
#1012110: pptviewlib does not accept unicode filename
#1199639: Formatting tags opened and closed in different verses throw an exception
#1206886: HTTP Server gets deleted
#1222534: KeyError when "Allow presentation application to be overridden" and Spanish language is selected
#1223841: Transition does not work if texts are the same
#1225763: Replacing background with video unblank screen even if "Blanked to Theme"
#1247661: Cannot restore OpenLP after minimising on OSX
#1251437: BibleGateway importer crashes on non unicode urls
#1258634: TypeError when saving service from previous versions with notes
#1259606: Clicking Verse Button doesn't alter live slide
#1266271: Output display returns after pressing esc when looping slides
#1157938: "Alt + Tab" = some pixelated icons and missing icons
#1211049: Can no long download bible verses
#1216234: Layout style has not effect when using a second bible
#1240942: Troubleshooting guide is outdated
#1265368: [regression] Traceback in web remote
#1163874: Add Slovak bible to First Run Wizard. (SK - Katolický (Písmo Sväté))
Stay dressed for action and keep your lamps burning, and be like men who are waiting for their master to come home from the wedding feast, so that they may open the door to him at once when he comes and knocks.
If anyone has had problems e-mailing either our support e-mail address or our bug reporting e-mail address over the last couple of weeks, we apologise for the inconvenience.
A few weeks ago we migrated some of our systems, including our web site, e-mail server and support system, to an new server for better performance and security. As smooth as the transition was, it wasn't 100% without error, and one of the small problems that we only discovered in the last 2 days was that some of our e-mails were not getting through to our new support system.
If you sent an e-mail in the last 3 or 4 weeks, and you never heard a reply from us (apart from an automated reply, perhaps), then please e-mail us again and we should now get your e-mails and be able to respond to your queries. If we still don't seem to be getting your e-mails, please visit us in IRC and let us know which e-mail address you sent your query to, and when you sent it.
Thanks for your patience, and your continued support!
A few days ago another open source church worship project called ExpoSong had to shut down. It seems to me that they had a very small development team and were unable to continue developing their software. ExpoSong's last release was over 2 years ago, in December 2011, and I can only presume they took a rain check as 2014 came round and decided to officially stop the project rather than leave it hanging.
It's very sad when an open source project has to shut down, but I can completely understand their position. Without time or resources to continue development, it is better to officially stop development rather than leave it open in the dwindling hopes that someone may have the time to continue at a later stage.
For those of you who have come from ExpoSong, I have put together a step-by-step guide below to show you how to easily export all your songs from ExpoSong and import them all into OpenLP. Click the Read more link below if you can't see the guide.
We have finally had some time to sift through the responses to the survey, and below I present to you the summary of the survey. There are some pretty graphs (for those who like graphs) and we've included the percentages of multiple choice questions. Note that due to most of the questions allowing more than one answer, the sum of the percentages will exceed 100%.
And so, without further ado, here are the results:
Update: The survey has been closed. We received 381 responses, and are busy processing the responses.
Before I kick off the main gist of this post, I'd just like to announce that OpenLP 2.0.3 has finally made it to our Ubuntu PPA.
Unfortunately I was having computer hardware issues and I wasn't able to get the build process set up until a few days ago. I've remedied this problem by setting up the build process on our Continuous Integration server such that anyone can build packages for the PPA by simply clicking a button.
As per the title of this post, we have set up a survey to help us decide on what the most important features are that we need to work on. This survey is completely anonymous, but we do ask that you only fill it out once. We've also set maximum number of features to choose so that we are absolutely certain that these are the most important features. Have your say: complete the survey.
We are happy to announce another bugfix release of OpenLP 2.0: version 2.0.3 "Patched Petrus". This release fixes a regression in OpenLP 2.0.2 where services with notes could not be saved, and includes some updates to the translations. Windows and Mac OS X builds are on the download page as usual, and OpenLP will filter down to the various Linux distributions over the next week or so.
As more minor bugs are brought to our attention, we will endeavour to make future bugfix releases of OpenLP 2.0 until OpenLP 2.2 is released. If you think you have found a bug, please check the list of bugs on our Launchpad.net project page to see if yours already exists in our bug tracker: OpenLP at Launchpad.net
Speaking of OpenLP 2.2 (and on a more technical note), we have completed the migration of OpenLP from Python 2.7 to Python 3.3. This was a big step for us, as Python 3 is not backwards compatible with Python 2, and we had to make some changes to the codebase to take this into consideration.
NB: While there will be ongoing talk of OpenLP 2.2, please do not use it for church! OpenLP 2.1 (the development version of 2.2) is unstable and WILL crash in the middle of your service. OpenLP 2.1 is NOT compatible with OpenLP 2.0, you may lose some or even all of your data. As soon as the code is more stable, we will start our release cycles again with alpha and beta releases for folks to try out.
It has come to our attention recently that some folks, in order to use the goodness of LibreOffice 4.1 on Ubuntu, are using a LibreOffice PPA (personal package archive) which causes OpenLP to crash on startup. This seems to be due to a bug in the way LibreOffice is packaged in the PPA, as other Linux users on distributions such as Fedora and Arch are not encountering the problem.
Please do not install LibreOffice from the PPA, it WILL break OpenLP.
Folks, please note that OpenLP is currently not compatible with LibreOffice 4.x on Linux due to the fact that OpenLP uses Python 2.7 and LibreOffice uses Python 3.2 which are incompatible. The next version of OpenLP, version 2.2, will be compatible with LibreOffice 4.x but unfortunately there is no way to backport this compatibility.
We have a Church of 30 people in Texas. And thanks to your software we are able to have the functions of the major projection software without the high cost. On behalf of Covenant Fellowship Church family, I wanted to say thank you to all the developers behind the OpenLP project.