Admin panel update notifier

After each release, we need to update some files IN TRUNK so Tiki installs are prompted to upgrade:

• doc/stable.version (where https://tiki.org/stable.version redirects and which is where all the Tikis connect to know if they should update)
• doc/regular.cycle
• doc/longterm.cycle

This exists in Tiki since 1.9.9 but has not always worked well throughout the versions. For example a Tiki admin needs to clear Tiki cache in their Tiki to refresh the remarksbox notice (about new upgrade available) above the control panels on the tiki-admin.php page.

Ref: Update notifier

Question: why are we also maintaining twversion.class.php?

Update tiki.org

A few pages here may need updating depending on the type of release:
https://tiki.org/Versions
https://tiki.org/Download

After the update, check tiki.org/tiki-plugins.php and see if any plugins need approval

1.1.3. Update dev.tiki.org

A few pages here may need updating depending on the type of release:

• The current development Tiki version page
• The future development Tiki version page
• Add new version categories
• Where To Commit
• SVN Usage (also maybe)
• Get Code (maybe)
• Daily Build (You need to ask Oliver Hertel to add new versions)

After the update, check dev.tiki.org/tiki-plugins.php and see if any plugins need approval

1.1.4. Update doc.tiki.org

• The current development Tiki version page
• The future development Tiki version page
• All-Releases page

After the update, check doc.tiki.org/tiki-plugins.php and see if any plugins need approval

1.1.5. Default Download at Sf.net

Set one of the new tarballs as the default file to download for Tiki project.

Setting the default download can be accomplished through the File Manager.

1. Go to the Files page while logged in to access the File Manager
2. From the File Manager navigate to the directory that contains the file
3. Select the "i" icon for the file you wish to set as the default download
4. On the bottom right check the boxes for the operating systems which you wish the file to be the default download for.
5. Select save

Some people say, that an image is worth a thousand words...

1.1.6. Update auto-installers

see https://tiki.org/1-click+installers and https://tiki.org/Distros if any.

1.1.7. Acknowledgements

• Make sure bug submitters (including security vulnerability reporters) are properly credited in the Tiki release announcements.

1.1.7.1. Previous release leftover.

It is critical the release manager double check that previous version (Major) have been through ALL the release step so nothing is forgotten. If some have been left it is time to complete and reduce the dissonance between what we have done and what should have been done following this page process list.

1.1.7.2. Version Page

It is important to communicate and log changes and improvement including updating the version page status (Checklist page, ie: https://dev.tiki.org/Tiki12#Checklist ).

1.1.7.3. Check external software library dependencies

It is always the good time to check and update any external components we have in Tiki.
Please refer to Check external software library dependencies section

1.1.8. Announce the good news on devel mailing-list

• Ask the Communications Team to launch the announce-spreading process as described on Communications Team Release
  • info.tiki.org/Download + news item +
    • the version numbers come from a dynamic variable: to edit, just click on the version numbers (as user with admin rights) and you'll be shown a text field where you can edit those version numbers.