FileSender

things making the install less then optimal

Set up automated test infrastructure using Selenium. The result should allow us to automatically test a FileSender version on a number of browsers. We want to make sure FileSender works for a set of specific browser - browser version - OS - OS version combinations: the supported browser matrix.

The supported browser matrix should list those environments typically encountered in the wild. The only way to scale up testing to the number of browsers is by automating. The goal is to prevent help desk calls to people running FileSender installs.

Automated testing enables us to test all versions at any time: nightly builds, betas, release candidates.

Stuff related to Assembla, sites etc. goes here.

Placeholder for new feature suggestions. Features go from "Suggested features" to "Planned features" if they are to be implemented.

temporary placeholder for the stuff in the workplan for 2011. Once we have prioritised the stuff here and the "smaller" tickets that were already planned or suggested, all stuff we work on goes into "planned" and "under development" as appropriate

Describe the goals for your next release

Establish easy-to-use infrastructure to farm out language file maintenance. Likely tool to use is:
https://www.transifex.net/tour/features/translate/

Adopting this tool likely means an effort to go from one format to the other. Until we have resources to do that, we'll work with an extra Assembla space.

Bugs found in 1.5 (currently under development)

Tickets filed under this milestone are features that are planned to be implemented

Version 1.1 is essentially FileSender 1.0.1 with the Gears module replaced by HTML5 upload.

Bugs found in version 1.0(.x) and the various beta releases before the 1.0 release.

Placeholder for bugs discovered in the 2.0 development

All features that are under development for version 2.0. Note that bugs get filed under a separate milestone (!)