Category Archives: FileSender 1.5

FileSender 1.5-beta3 available!

On May 15, Xander Jansen announced the availability of the 3rd beta of our upcoming version 1.5. Please help us by field testing it!  If you discover any issues, please report them to our support mailinglist.

This week Xander, Guido and myself are gathered at the 2012 TERENA conference.  We’ll discuss further planning of the 1.5 release, taking into consideration the security audit report we expect to receive tomorrow.  Most likely there will be a beta4.

Xander’s announcement:

“We’re happy to announce that FileSender 1.5-beta3 release is now available for download and in the FileSender package repositories.

Version 1.5-beta3 is the third beta release for the upcoming 1.5 version and contains mostly what we refer to as “cosmetic fixes” regarding the user interface, user feedback and error reporting and logging.

Be sure to read:

http://www.assembla.com/spaces/file_sender/wiki/Installation_notes_for_1-5_development_code

for installation and upgrade notes.

Download details are at:

 http://www.assembla.com/spaces/file_sender/wiki/Release_1-5-beta3

Changes since 1.5-beta2:

  • HTML5 upload support for the upcoming FireFox 13.
  • Improvements in the User Interface.
  • Improved user feedback and error reporting
  • Improved server side logging.
  • Various small bug fixes and enhancements.

Changed features:

  • Option to securely wipe (shred) expired files in the daily cron job.
  • Separate text definitions for ‘logon’ button and title of the landing page.
  • The configured ‘Site Name’ is now used on the landing page.

As usual many thanks to all contributors to this release for their patches, comments and translations! Please keep them coming!

On behalf of the FileSender team,

Xander”

Thanks Xander!

Status FileSender 1.5, 26 april 2012

Yesterday FileSender 1.5-beta2 was released.  We believe  to have fixed all backend issues: those with an impact on the database, program flow or I/O pathways.

From hereon I estimate it will take 2 additional betas before we are ready for releasing.  Our path towards the 1.5 release is:

  • beta-3 is planned as a “fixed date release” for May 15th and will contain mostly what we refer to as “cosmetic fixes”.  Crucially important for the user experience, but less of an upgrade impact for sysadmins.  We’ll knock off open tickets labeled “1.5-beta3” until the 7th of May, after which the workflow-test cycle is run, changesets are merged into the right spot of the code tree and the release is ready on May 15.  Remaining issues will be scheduled for beta4.
  • the external code security auditis planned to be executed between 9-11 May, with the report expected around 18 May.  An external security audit is part of our release status and life cycle policy: despite our attention for security we do have blind spots.  The external security audit is there to make sure FileSender does not have any “basic” security issues.  Based on this report we can schedule beta-4.
  • beta-4 is a tentative beta, depending on the results of beta-3 and the security audit.
  • the first release candidate RC1 is the rebrand of the last beta.  There is a period of at least 1 week between release candidate and the “final release”.  We use this week for final quality assurance and wrap-up of documentation details.

Please check the Release Schedule for details and up-to-date planning.

FileSender 1.5-beta2 available!

Today our release manager and chief code-repository Xander Jansen announced the availability of the 2nd beta of our upcoming version 1.5. Please help us by field testing it!  If you discover any issues, please report them to our support mailinglist.

Here’s Xander’s announcement:

“Hi,

We’re happy to announce that FileSender 1.5-beta2 release is now available for download and in the FileSender package repositories.

Version 1.5-beta2 is the second beta release for the upcoming 1.5 version and contains some important changes concerning the installation and configuration, most notably the language definitions.

It is recommended to start with a fresh install although upgrading from previous versions (1.5-beta1 and 1.1) is also possible. Be sure to read the Installation notes for 1.5 development code for important installation and upgrade notes.

Download details are at:

http://www.assembla.com/spaces/file_sender/wiki/Release_1-5-beta2

The most noticable new features/changes since 1.5-beta1 are:

Major changes since 1.5-beta1

  • The ./config directory as distributed now only contains a sample config-dist.php file. All other templates/sample files have been moved to ./config-templates or their contents have been merged into the ./language/* files.
  • The supplied config-dist.php has been cleaned up and contains some important changes. It is recommended to create a fresh config.php from the supplied config-dist.php file and adapt that one with your local settings.
  • Two database column type changes (needs manual adjustment when upgrading).
  • Changed and consolidated language file naming scheme.
  • Added Czech, Slovenian, Italian, Spanish, Croatian and Hungarian language files.
  • Updated Dutch and Norwegian language files.

Major (less visible) changes since 1.5-beta1

  • Further improvements in workflow, validation/error handling and input/output pathways.
  • Minor bug fixes and enhancements.

Many thanks to all contributors to this release for their patches, comments and most notably the translations!

On behalf of the FileSender team,

Xander”

Thanks Xander!

Status FileSender 1.5, 30 March 2012

FileSender 1.5-beta-2 has been delayed due to factors outside of our control.  The new planned release date has been set to 15 April.

We do appear to make good progress on automating the client-side testing with Selenium.  Go Wendy!

 

Status FileSender 1.5, 13 March 2012

A short status update after todays conference call with Chris, Xander and myself.  No major dramas were uncovered during the last week.

The past week we worked to fix bug ticket 641  (multi-tab session management) but that turned out to involve so many code changes we decided to not let this delay release of version 1.5, and rather issue an update later this year.  For those of you providing FileSender services: the issue is also present in older FileSender versions.  It’s a corner case that pops up when a guest user uploads multiple files in multiple tabs in the same browser.

We went through the remaining issues and believe we’re on track for releasing beta2 next week.  If you want to help us, please test that version.  The fixes planned after beta2 are mostly cosmetic so if anything serious is waiting to be uncovered, we need to uncover it now.

Status FileSender 1.5, 6 March 2012, beta-2 planned

In today’s conference call  Chris, Xander and myself went through open bugs and beta-planning.  We plan to release  FileSender 1.5-beta2 in the week of 19 March.

Aside from a number of smaller improvements, beta-2 is expected to provide:

  • all localised content folded into one language file
  • improved upgradability by re-arranging “distribution-files” and “local overrides”
  • improved upload robustness by taking care of multi-tab upload session management

Planning of the security audit is well underway: a statement of work  is done, and we’re awaiting the quote.  The audit is expected to take place early April.

Based on our current assessment of code quality we expect the path to the 1.5 release to be:

  • beta-2
  • beta-3
  • RC1 (release candidate)
  • Release

Please note a security audit might necessitate work resulting in a slightly different release schedule.  Our most current planning is always available on the release schedule.

Lastly, we’ve decided to set up a separate Assembla space to manage maintenance of language files.  We have a different tool in mind for the longer term (Transifex) but that’ll require some time to integrate with our processes and code.

Please direct any questions to the filesender-dev list or to one of the project leads.

FileSender 1.5-beta1 available!

Our release manager Xander Jansen has just announced the FileSender 1.5-beta1 release is available for download and in the FileSender package repositories. We invite you all to try this beta1 and let us know about any issues (positive and negative) you may have. Points of interest are ease of installation (most notably using MySQL as backend), browser compatibility, upload stability and user interface.  We hope a number of you will be able to conduct proper field testing with representative users to allow us to see how the software holds up in the wild.

Download details are at:
  http://www.assembla.com/spaces/file_sender/wiki/Release_1-5-beta1

Version 1.5-beta1 is the first beta release for the upcoming 1.5
version, we anticipate at least one more beta release.  As the detailed planning materialises, the planning dates can be found on the release schedule.  The most noticable new features/changes since 1.1 are:

Major changes since 1.1/1.0.1

  • Replaced Flash User Interface with a HTML-only interface
  • Dropped Gears dependency, upload of large (>2G) files now requires
  • a modern HTML5 capable browser, other browsers are limited to 2G
  • uploads (using a small Flash-application).
  • Added automatic language selection (English, Norwegian, Dutch)
  • Added Database Abstraction Layer (PDO) to facilitate the useof MySQL and possibly other databases as backend.

Major (visible) changes since earlier 1.5.0 development builds

  • Added French and German languages (contributed by RESTENA), Italian is scheduled for the next beta
  • Replaced MDB2 with PDO DB Abstraction Layer

Major (less visible) changes since earlier development builds

  • Input/output pathways have been simplified
  • Input/output sanitisation and validation is done
  • Much code and program flow has been cleaned up and simplified
  • We now use mostly prepared statements for database interaction
  • All pages are now W3C compliant

Please provide your feedback, positive and negative, to the filesender-dev mailinglist or directly to the filesender-core team.

In the 6 weeks to come we will work to squash the remaining bugs, preparing for 1.5-beta2.  That includes preparing the documentation and organising a code security audit.

Thank you Xander for providing most of the text for this blog article 🙂