After all the leasons learned from developing the HTML5 parts of FileSender 1.5 Chris was curious to see whether he could get the current 1.0.1 code to support HTML5 uploads, with little effort. Leveraging the similarity between Gears calls and HTML5 FileAPI calls he managed to backport the HTML5 functionality to the current 1.0.1 code 🙂
The trunk now contains 1.0.1 HTML5 patch that replaces Gears with HTML5, adds one crucial little detail to the uploads page and removes the Mac “uploads > 2GB are not supported” message. There is one minor issue with progress bars overlapping, other then that it appears to work just fine.
We now have an opportunity to use Chris’s 1.0.1 HTML5 patch for creating an interim release based on the stable and well tested 1.0.1 code that supports >2GB uploads without Gears. Barring service affecting issues popping up during the quality assurance process such a release should be ready in about two weeks.
Given that FileSender 1.5 will go through a quality assurance cycle before releasing, a fully tested production release of 1.5 will not be available before December.
We feel offering production sites the option to run a FileSender service without the Gears dependency is important enough to to test and package the HTMl5 patch into a “FileSender 1.0.1 Fall 2011 Special” release. This special release will be packaged and distributed under a separate
name (filesender-html5) and will have the same version number (1.0.1) as the current production release. We estimate this to take about 4 weeks of lead time. The testing, packaging and release process of the Fall 2011 Special will not involve our developers, they will continue to focus on the 1.5 release.
Why not a “FileSender 1.1” you might wonder? One of our guiding principles is POLA, the Principle Of Least Astonishment. We’d hate to create unexpected surprises for production sites when releasing. A FileSender 1.1 release would trigger a near-automatic upgrade for those of you using the Debian or RPM package. For reasons of your own you might not want to upgrade, you might be happy with 1.0.1 as is. By releasing a one-off special package you have the choice.
The extra support load of having two 1.0.1 releases to support is pretty minimal: we only fix crucial service-affecting bugs in 1.0.1 (none have surfaced so far) and thought the release package will take some months to ship the 1.5 release is in its last stages of development.
To sum up, under the assumption that thorough testing won’t reveal any service affecting issues, we’ll have a FileSender 1.0.1 release without Gears dependency in about 4 weeks. This special release will be packaged and distributed under a separate name (filesender-html5) and will have the same version number (1.0.1) as the current production release.
It won’t be perfect, but it’ll do the job.