History: Packaging Team
Preview of version: 39
The Packaging Team involves making Tiki easily deployable on various platforms and 1-click installers.
Release responsibilities
- Run Release scripts for packaging all releases (Alpha/Beta/RCs/Official)
- Make sure everything is OK with Packages
- Submit to and keep up to date each of the 1-click installers and Distro
- Maintain Installation guides
Urgent
- Coordinate with Bluehost / SimpleScripts
-
Tax info from Finance Team - Versions are outdated: https://www.simplescripts.com/script_details/install:TikiWikiCmsGroupware#versions (+ LTS discussion)
-
Tasks
- Coordinate with Bitnami (Greg Martin)
- Coordinate with Cloudways (Greg Martin)
- ISPConfig now offers "APS package installer", but APS is still offering Tiki 3.x
Ongoing
- Coordinate with 1-click installers (Marc)
- Microsoft Web Platform installer WebPI coordination and package updates (Greg Martin)
- Relations with Microsoft (Pascal St-Jean of Partnership Team)
- Keeping things tidy at https://sourceforge.net/projects/tikiwiki/
- Move old stuff to the Old_Stuff folder: https://sourceforge.net/projects/tikiwiki/files/
- Make Tiki the best possible platform for a hosting company
Projects
- Negotiate with hosting companies for hosting and affiliate agreements (Marc)
- Testing Tiki installations on major Shared Hosting companies (Marc)
- Remove stuff from the package
- doc/stable.version
- unstable.version
- Replace changelog.txt with a link to tiki.org/Changelog, which itself redirects to SourceForge's SVN view
- Improve the release process
- Improve Tiki Server Check
- Improve Tiki Permission Check
- Improve the installer
- Reduce disk space
Todo
-
Tiki is not working on WebPI 3.0 - Related to Testing Tiki installations on major Shared Hosting companies, investigate for a way to set permissions properly from the .zip Ex.: on http://bluehost.tiki.org/92b1/, there was an error 500 until sh setup.sh was run
Related