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.