Release Process

Release early, release often. This is a mantra from free software communities. It's accurate. You want to do your design work in the open, and get critical feedback as early as possible.

1. Stages

alpha1
- Alpha is for preview purposes only.
- it is intended to be a technology preview aimed at early adopters, testers, translators
- Do not use alpha releases on production systems!
alpha2
beta1
- Beta releases are appropriate for use with new development. Within beta releases, the features and compatibility should remain consistent. However beta releases may contain numerous and major unaddressed bugs.
beta2
- is available for testers, extension developers, and other people who are curious to follow the development of the next release
rc1
- Release Candidates are believed stable, having passed all internal testing, and with all known fatal runtime bugs fixed. However this release has not been in widespread use long enough to know for sure that all bugs have been identified.
  - wait to declare something RC until code stabilizes and critical bugs are fixed
- feature freeze -> testing and debugging ->
  - This release is ready for widespread testing, and we’re encouraging everyone to download and test the beta releases. Please run the release through your usual routine, and let us know about any bugs or other issues that you find. Remember that this is a beta release, and is not suitable for use on production systems.
- For translators, this is the first call to update the translations to the current set of strings, which should not change much until final.
rc2
final
- also know as Production releases, are stable, having successfully passed through all earlier release stages and believed to be reliable, free of serious bugs, and suitable for use in production systems
- All users are advised to upgrade.
m1
- Maintenance release

2. Issue tracker

update issues in bugtracker
set release date

3. Change Log

Could not load or parse feed
cURL error 22: The requested URL returned error: 500

4. Release Notes

Upgrade from previous versions
- Component compatibility
- Configuration
Highlights
Call for Localization
- If you can help with languages other than English and German, it would be appreciated.
Testing
- Most Annoying Bugs
  - While many bugs have been eliminated since the last beta, we still have a few remaining (and new) bugs that testers should be aware of:
Themes
Hacks / Patches

5. Build packages

tarball
zip
name the folder within the package according the release
- wacko.r6.0.34
- wacko.r6.1.26
- wacko.r7.0.1

Set back error reporting level in constants.php

const PHP_ERROR_REPORTING			= 0;

Set back error SQL mode to permissive in config.php

'sql_mode_strict' => '0',

6. Repository

tag the release
branch final release

7. Update Files

Latest development version
Latest released testing version
Latest released stable version

7.1. Update file references

wackowiki-6.1.26.zip^[link1] (2.3 MiB)

Development version
wacko.tar.gz^[link2] (see Repository^[link3])

8. Release notices and announcements

SF.net file release system's e-mail notices
Announcement -mailing list
SF.net Project news
Draft the new release on GitHub
- https://github.com/WackoWiki/wackowiki/releases
Web pages
- https://freshcode.club/projects/wackowiki

Links

[link1] https://downloads.sourceforge.net/wackowiki/wackowiki-6.1.26.zip
[link2] https://bitbucket.org/wackowiki/wackowiki-dev/get/tip.tar.gz
[link3] https://wackowiki.org/doc/Org/Tools/Repository