Software Packaging

The first technology-related activity is to produce the software package to be tested by beta testers during the campaign.

Whatever the maturity of the project a proper package must be offered to beta testers, not just the code on the repository.

Software to be beta tested should be easy to access and to deploy. The software must be easily consumable by third-party IT professionals. The beta version must be properly packaged.

While deployability might be right in the scope of beta-testing, complex build processes are a huge deterrent and must be avoided at all cost. Depending on the scope a SaaS instance of the software will facilitate beta testers participation, otherwise Docker images are also a good practice.

As a packaging option, ReachOut offers project the possibility to use the ReachOut Factory to package their beta version.

And of course, if the software has to be deployed a download link must be easily accessible and operational.

And if it is a service, proper user management must be in place.

The beta version must be validated by internal beta testers and the support contacts appointed among project participants.

The Reachout project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement number 825307.

flagEU.svgThe information in this document is provided “as is”, and no guarantee or warranty is given that the information is fit for any particular purpose. The content of this document reflects only the author`s view – the European Commission is not responsible for any use that may be made of the information it contains. The users use the information at their sole risk and liability.

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 9.11.8 - Documentation