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.
- 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.
- 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
Feed Title: Release notes from wackowiki[link1]
6.1.19[link2]
Minor feature and bug fix release for 6.1.x series
- improves MIME type check and verify file extension check in upload handler
- fixes file tool visualisation for
allandlinkedmode - moves page tag pattern and file extension sets to constant array (
self::PATTERN) - moves
wacko_languageintowacko_translation - adds
upload_allowed_extsoption to config - adds file hash to
filetable (set missing file hash for legacy records viaadminupdateaction) - adds duplicate file notices
- skips now
is_executable($dir)check for Windows in restore module - svg-sanitizer 0.15.4
- miscellaneous minor fixes
6.1.26[link3]
Minor feature and bug fix release for 6.1.x series
- adds
file_metaforfile_cache - uses
:focus-withinpseudo selector for dropdown - adds CSS class
btn-smandbtn-md - English message sets fixes
- initial language files for Tamil
- re-check for anonymous user before storing cache
soft_login()may setsess->user_profile
- removes redundant
setlocale()call - adds
db_vendorto primary config - installer auto-detects
db_vendor- either
mariadbormysql - uses server SQL mode for installer by default
- in
debugmode thedb_vendorcan be selected in the db config page along with the SQL mode - mainly to solve SQL mode incompatibilities between MariaDB and MySQL
- either
- renames
sql_mode_stricttosql_mode0- server (default)1- session lax2- session strict
- fixes not showing read ACL
$pages in the default menu for logged in users with no own bookmarks defined - miscellaneous minor fixes
- svg sanitizer 0.19
- PhpThumb 2.3.1
6.1.24[link4]
Minor feature and bug fix release for 6.1.x series
- sets direct link to diff handler in feed and change notice
- sets
abuse_emailas the Sender email (return-path) of the message - updates Português translation
randomaction redirects logged-in users now also to pages with registered users as read permission- enables section edit by default
- adds syndication module to Admin panel
- miscellaneous minor fixes
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:
- Most Annoying Bugs
- Themes
- Hacks / Patches
5. Build packages
- tarball
- zip
- name the folder within the package according the release
- wacko.r6.0.34
- wacko.r6.1.27
- 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.27.zip[link5] (2.8 MiB)
Development version
wacko.tar.gz[link6] (see Repository[link7])
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
- Web pages
- Feed
- [link1] https://github.com/WackoWiki/wackowiki/releases
- [link2] https://github.com/WackoWiki/wackowiki/releases/tag/6.1.19
- [link3] https://github.com/WackoWiki/wackowiki/releases/tag/6.1.26
- [link4] https://github.com/WackoWiki/wackowiki/releases/tag/6.1.24
- [link5] https://downloads.sourceforge.net/wackowiki/wackowiki-6.1.27.zip
- [link6] https://bitbucket.org/wackowiki/wackowiki-dev/get/tip.tar.gz
- [link7] https://wackowiki.org/doc/Org/Tools/Repository