Geeklog Release Procedures
This page outlines the necessary steps to perform before, during, and after the release of a new Geeklog version.
- Obviously, plans for a new release should have been discussed on geeklog-devel. For security releases, the discussion may happen on geeklog-security only.
- Notify the geeklog-translations mailing list to give translators a chance and a timeframe to update their translations.
- Make sure you update history file in docs with version and release date (and readme in root directory if needed)
- Confirm correct Geeklog version number in /public_html/sitconfig.php, /public_html/admin/install/classes/installer.class.php, and /build.xml
- Make sure all language files are synched
- This process will use the English language files and synch with all other languages for Geeklog, The Installer, and all core plugins
- Open your command prompt and to the top directory of your local Geeklog repository
- Type: .\system\build\vendor\phing\phing\bin\phing.bat lang
- Once complete commit any updated language files
- For building an install package we use phing (which uses a config file called “build.xml” in the top directory).
- Go to your Geeklog repository top directory in command prompt
- Confirm latest repository and make sure no old compressed install packages exist (or they will be rolled into the new package).
- Type: .\system\build\vendor\phing\phing\bin\phing.bat dist
- Once the process complete you will get a file “geeklog-2.1.2.tar.gz” in the top directory
- If this is a beta or release candidate then the file will need to be renamed to: geeklog-2.1.2-b1.tar.gz or: geeklog-2.1.2-rc1.tar.gz
- Create a new release on GitHub
- Visit https://github.com/Geeklog-Core/geeklog/releases
- Create a release and make sure to tag it the correct version number (it will be tagged in the repository), for example: v2.1.2 or v2.1.2-rc1 (for release candidate) or v2.1.2-b1 (for beta)
- Visit Geeklog.net
- Add the new release to the downloads plugin
- Add a new article about the release pointing to the correct download
- unpack tarball on the server
- update site
- IMPORTANT: Disable Bad behavior plugin before upgrading Geeklog.net and then re-enable after. If you don't it may cause issues.
The following files need special handling when updating geeklog.net:
- As of Geeklog 2.1.2 the glnet_curve is now the default theme used by Geeklog.net. It is a copy of on the Denim Curve theme with only a few changes to the header and footer template files (along with the name changes, etc.. required in functions.php). This theme is based on the Denim theme which is also required in the themes directory. No other themes should be present on Geeklog.net.
- On upgrades for the glnet_curve remember to update the jquery_ui directory and the images directory with any changes from the Denim Curve theme. The fonts, css, css_ltr, and css_rtl directories are also required.
- As far as template files are concerned only the files we modified directly for Geeklog.net should be in the glnet_curve directory and the Denim theme should be the stock theme from the release. Most changes in these files are marked with the"GLNET CUSTOM" comment.
- For glnet_curve theme take a copy of the footer.thtml from denim and add it to glnet_curve. Make sure the version number is visible and add the "hosted by pair.com" link (as per our agreement with pair Networks).
- The Download block on the top right uses a block header template without a title, so add this to the theme's functions.php:
$_BLOCK_TEMPLATE['download'] = 'blockheader-notitle-right.thtml,blockfooter.thtml';and make sure the blockheader-notitle-right.thtml template file exists.
- remove the bundled lib-custom.php and robots.txt and use the copies already present on the webserver instead
- If updating lib-custom make sure to add the functions phpblock_current_versions_downloads and phpblock_whos_new
- check db-config.php and siteconfig.php for any required changes
- If you change the database name on the Geeklog upgrade (which we have been for each new version) remember to change the cron-jobs to reflect the new database name, username, and password
Information to Update
- Create a new download for the install in the Downloads plugin. Easiest way is to copy and older version of a Geeklog download.
- A full install tarball download belongs in the Geeklog category and the Geeklog project. An Update tarball belongs in the sub category Updates.
- Make sure any release previous betas or release candidates are moved to Old Versions Downloads category.
- Confirm Downloads button on homepage block points to the latest Geeklog download.
- Publish an article on geeklog.net:
- summarize the changes in this release
- include a link to the entry in the download area
- Convention for the story ID: geeklog-x.y.z, e.g. geeklog-1.5.2, geeklog-1.4.0sr6
- Add story to the Geeklog topic and the Announcements topic (default). Make sure both are set to inherit
- Announcements of new versions go into the Announcements topic. For security releases, either post the announcement in the Security topic, or post two articles (one in Announcements and the details of the security issues in Security).
- don't forget to send pingbacks and ping weblog directories
- Update the versionchecker.php script (not for betas/release candidates).
- Once updated, the new version of the script should be added to the tools repository.
- Send out an email to the geeklog-announce mailing list.
- Provide a brief description of the release and link to the geeklog.net article for details.
- Update the wiki frontpage (not for betas/release candidates)
- Update the GitHub Issue Tracker (not for betas/release candidates). Make sure you have a later milestone create and then move all incomplete issues and feature requests from current milestone to a later milestone. Close current milestone
- Notify Ironmax at Spacequad.com that the demo site needs to be updated to use the latest version of Geeklog (not for betas/release candidates). Once updated you will also need to update the Resources block with the correct version number of the demo site.
These sites should only be notified about final and security releases (i.e. not for betas and release candidates):