In the series “milestones” I present you SVN commit number 1000, commited on 2011/10/24 13:34 by Xander Jansen. Congratulations Xander on a nice round number, and many thanks for all your contributions!
What was recently announced as the FileSender 1.0.1 Fall Special with HTML5 has been relabeled to FileSender 1.1.
Following the initial announcement we (the filesender core team) struggled a bit with the logic of our choice; something in it didn’t make 100% sense. Replacing Gears by the HTMl5 FileAPI is a quite significant change on a production service that changes the way users do uploads >2GB.
After thorough discussion we felt it was better to indicate such a significant change in functionality with a clear version number increment. In addition this made it a lot easier to fit this version in a logic software release life cycle and to push it out in an orderly fashion through the debian and RPM repositories. Last but not least the Google Gears website now mentions “Gears is deprecated and will no longer be available as of December 2011.” We read this as “from December 2011 there will no longer be a well-known point where users can download the Gears plugin. That means any FileSender site using Gears for uploads larger then 2GB will have a problem with new users. This obviates the need for a clear FileSender 1.0.1 phase-out plan, and a clear successor. Thanks to Chris we have FileSender 1.1 to fill that position.
So FileSender 1.1 it is. We expect to release within the next weeks. Testing is done, AARNet is field-trialling it in its production environment. What remains is finalising the packages and some loose ends in the documentation. If you’re interested in joining AARNet and running the 1.1 code before its final release, please drop us a line. In addition to going from Gears to HTMl5 it’ll contain a number of very minor bugfixes that’ll take away some annoyances reported since we released version 1.0.1 in May 2011.
We’ve used the effort we put in thinking this through as an opportunity to write down a first take on a FileSender software release life cycle. That should make the process of releasing FileSender 1.5 and follow-up versions more predictable and taking less “process” time of the core team.
I’ll be offline next week and will publish the FileSender software release cycle probably the week after that, together with an update on where we are with FileSender 1.5 and when you can finally expect that beta.