Author Archives: janmeijer

FileSender showcase at GÉANT upgraded

GÉANT, the European NREN membership organisation, has been operating a FileSender show case installation for many years. Accessible through a wealth of login options it offers anyone curious a chance to give FileSender a try.

https://filesender.geant.org/

This installation was upgraded last week to the latest software release and with that has joined the growing number of FileSender sites running the 2.x version.

Thanks GÉANT!

 

New release v2.11 – encryption hardening

Version 2.11 of the FileSender software was released on 4 November 2019 and is available here:

https://github.com/filesender/filesender/releases/tag/filesender-2.11

This release’s main improvements are the hardening of the end-to-end encryption functionality. Please see the release notes at the URL above for details.

Video of FileSender presentation at linux.conf.au 23 Jan 2019

FileSender tech lead Dr. Ben Martin presented FileSender at the January 2019 Linux.conf.au conference. For anyone new to FileSender this presentation provides an excellent overview of all functionality of the software.

Video of presentation:

 

Dr. Ben Martin presents FileSender at NLUUG Fall 2018

FileSender tech lead Dr. Ben Martin presented FileSender at the November NLUUG 2018 fall conference in the Netherlands.

Video of presentation:

FileSender space on Assembla phased out

Since we started FileSender back in 2009 we’ve used the Assembla platform to host all important data for the project in a central place: documentation, tickets, files, source code.

As of today the FileSender project space on assembla.com no longer exists. All existing data (wiki, tickets) has been captured and made available (read-only) on Github in a separate repository: https://github.com/filesender/assembla-export

We believe the data that still was on the Assembla space all pertained to version 1.x releases, which we are no longer maintaining. We will keep the old data on Github for historical reference. If there is anything you’re missing from the old Assembla space, please let us know on filesender-dev@filesender.org. If you believe it needs to be put on the current docs.filesender.org website, the fastest way forward is to create a markdown (.md) file with the content and submit it as a pull request.

Why the Assembla phase-out?

Those of you following the FileSender programme know we have been moving away from Assembla for quite some time. We moved the code from Assembla’s SVN to Github in September 2016. We then moved all version 2.0 documentation and the main project landing page to Github and publish both through github.io. s well and publish it through github.io on docs.filesender.org. and www.filesender.org. Last but not least we have been using the Github issue tracker for all v2.0 development since we moved the code.

Until recently there was no cost associated with keeping the old Assembla project space alive. Assembla changed this in August this year when they introduced their new subscription model where free spaces for open source projects were no longer an option. When this happened we decided to fast-track the shut down of our Assembla space. It served us well but it’s now time to move on.

Alpha, beta, release candidate and production releases

We haven’t really made a line-in-the-sand release announcement of version 2.0-alpha. This was partly because we didn’t really have a good definition of what we mean by an alpha release and how it’s different from a beta release. This post is intended to clarify this and to ensure that our community has the right expectations of our various releases. The related pages at www.filesender.org will be updated shortly. We would appreciate community feedback on this blog post: please let us know whether our definitions match your expectations via the filesender-dev mailing list.

A release goes from “a bucket of code”, through “alpha”, “beta” and “release candidate”, to production “release”.

Characteristics of a FileSender alpha:

  • Draws a line-in-the-sand from where development will move from “adding to a bucket of code” towards “getting code and documentation to a production release state”.
  • Has adequate installation documentation but may require more installation and configuration effort from a system administrator than a production release will.
  • Has not undergone structured client-side workflow testing.
  • Must be assumed to have unknown issues.
  • The feature list is mostly stable but can change.
  • Documentation is typically incomplete.
  • Has been through some basic tests by developers: usually this means automated unit tests on software components, and verification by the developer and verification on an independent installation installed from Subversion (SVN) that at least the most basic functionality (uploading and downloading of a file) proceeds as intended with at least one browser.
  • Is released through SVN. We want the community to be able to update their alpha release based installation as soon as new code is available and without too much hassle. Inserting a packaging step before releasing alpha versions would delay and further complicate the alpha release procedure.
  • Release announcement includes the SVN branch name and revision number – it is that specific SVN checkout that is considered to be the specific alpha release.
  • There can be multiple alpha releases. They will be labelled alpha-1, alpha-2 etc..

Characteristics of a FileSender beta:

  • Has undergone some structured client-side workflow testing.
  • Should be easy to install and the tested features should simply work.
  • Feature list is being stabilised. This implies a new-feature freeze when releasing the first beta. It also implies a documented understanding of the feature list by the last beta release.
  • A summary of structured client-side workflow tests conducted per beta release typically indicates which features have been tested and with which browser(s).
  • You should not encounter unknown issues in tested features. Note that not all features may be tested for a particular beta release.
  • Is at a minimum released as a tarball.
  • There can be multiple beta releases. They will be labelled beta-1, beta-2 etc..

Release candidate:

  • At some point in the release cycle, the list of all features that we wish to ship in a functional state should be documented and collectively present in one single beta release. After that particular beta has undergone structured client-side workflow testing and been released, and has also proven itself stable in field testing, this beta release can become a release candidate.
  • This is the release where we are confident that we have identified the important known issues and that there are no show-stopping issues.
  • Small bug fixes since the last beta release can be added to the release candidate.
  • Is at a minimum released as a tarball.
  • After release will be field-tested on at least two FileSender release candidate test sites:
    • Production sites with at least X transfers by X unique users per day.
    • The sites run with well-known configurations making what are considered standard features available to their user bases.

Release:

  • Once a release candidate has been running production traffic with live users for at least two weeks on at least two release candidate test sites and shown no significant issues impairing service for the users, it can become the production (major) release.
  • There are no code, database or configuration file changes between a release candidate and a release.
  • Is at a minimum released as a tarball.
  • At some point(s) prior to a production (major) release, the code has been subjected to at least one external code security audit.

 

The following pages will be updated as part of this policy clarification:

We would appreciate community feedback on this blog post: please let us know whether our definitions match your expectations via the filesender-dev mailing list.

FileSender 1.6.1 released!

We’re happy to announce that FileSender 1.6.1 is now available for download and in the FileSender package repositories.

This is a bugfix release correcting the Safari 9.0.x upload problem and a XSS-vulnerability in the admin page. It is recommended to update as soon as possible.

Changes since 1.6

  • Fix: upload problem with Safari 9.0.x (#1217)
  • Change: new HEAnet and UNINETT logo (#1218)
  • Security: escape PHP_SELF variable in admin page (#1240)

Download details

Documentation

https://www.assembla.com/spaces/file_sender/wiki/Documentation_v1-6

Upgrading from a previous (major) release

If you are upgrading from a previous (major) release be sure to read the important installation and upgrade notes:

 https://www.assembla.com/wiki/show/file_sender/Upgrade_notes

Feedback

Please use the filesender-dev mailinglist for feedback, bug reports and comments