Dan and I periodically get together to have a look at progress with the project, and last night was the first chance I had to see the work Dan has been doing over the past few months towards the first in the 1.1 testing release series.
All I can say is wow! There’s support for translations (thanks to everyone who’s contributed translations so far over in Launchpad), display groups, overhauled permissions system, overhauled user login/sessions, and now he’s in the middle of redesigning the GUI for scheduling (and in fairness I probably missed some bits too).
Progress is also good on my baby, the cross-platform client for Xibo based on libavg and written in Python. I’m in deep with the webservice code at the moment, which is the final step in making it basically functional. We’ll then need to crack on with getting webpage support in to libavg. There’s some really nice features coming – region layering, transparency (including alpha transparency on images and video), webcam/firewire camera support, region and layout transitions and maybe even some basic animation.
Andy Pattenden has been busy too building some CC licensed backgrounds and other assorted artwork for the project (watch out for analogue clocks in 1.2!), and Jim Packer is busy tidying up the excellent theme he made for the website.
There’s a VMWare Appliance for Xibo in the pipeline thanks to Terry Bradford.
There’s also a fair number of bugs that have surfaced in 1.0.2 so we’re busy working towards a 1.0.3 release for both server and client in the near future.
And to cap the post off, I see we’ve hit 300 Xibo installs ever (that we know of). Thanks to you all for your feedback. We read every single email, bug report, blueprint and forum post – but there’s a mountain to climb and we’re prioritising boring “under the hood” work at the moment that will mean the shiney stuff later on will be easier to implement and maintain.
Dan and I spent about 4 hours today going though all the Blueprints (feature requests) we’ve had since releasing Xibo, and considering them for inclusion in the 1.0 and 1.1 series.
I think here it’s worth explaining how we’re going to proceed after 1.0.0 is released.
- 1.0.x will be stable releases of Xibo, and will have no new features. We will continue to backport bug fixes in to this series. Only the current Windows .net client will be available for use with 1.0.x (officially anyhow!). You can see a list of bugs and blueprints that we have targeted for 1.0.0 here: https://launchpad.net/xibo/+milestone/1.0.0
- 1.1.x will be an unstable development series. This is where all the development work for 1.2.x will happen. There will be releases of 1.1, but they will not be recommended for production systems. We’ve got lots of good stuff lined up for the 1.1 (and ultimately 1.2) series. You can see what we have targeted so far here: https://blueprints.launchpad.net/xibo/1.1
- 1.2.x will be the next stable release series for Xibo replacing the 1.0.x series of releases. This will be the culmination of the 1.1 series, and will almost certainly be preceded by some release candidates (as 1.0.0 was)
Items we’ve targetted for 1.0.0 are pretty well finalised now, and we hope to release 1.0.0 fairly soon. Items we’ve proposed as goals for the 1.1 series are far more fluid, and may slip.
Thanks to everyone who has filed bugs, written or suggested blueprints.
We’re hoping to have Xibo 1.0.0-rc3 ready for general release later today.
The latest release will address some issues that were found using Xibo outside it’s native UK timezone.
With Xibo in such early stages, we strongly recommend everybody to upgrade to 1.0.0-rc3 – but especially if you are using Xibo in a non-UK timezone.
We are aware that 1.0.0-rc3 will still show dates in EU format (ie dd/mm/yyyy), and that it is not currently possible to customise this. There is a blueprint in Launchpad to track this work in conjunction with some changes we already wanted to make to how the calendars are displayed. Please feel free to subscribe to the blueprint to keep track of how we are progressing on this.
Thanks to everyone who has reported these issues to us. Look out for the release soon!