Geeklog Release Procedures - Revision history

Tom: /* Geeklog Sites */

2020-04-16T15:07:36Z

‎Geeklog Sites

2020-04-16T13:31:44Z

‎The Tarball

2020-02-27T12:00:29Z

‎Updating geeklog.net

2019-12-18T15:23:50Z

‎The Tarball

2019-11-15T17:33:17Z

‎The Tarball

2019-11-15T16:47:29Z

‎The Tarball

2019-11-15T16:47:14Z

‎Updating geeklog.net

2019-11-15T16:44:14Z

‎The Tarball

2019-11-15T16:43:35Z

‎The Tarball

2019-11-08T17:44:13Z

‎The Tarball

@@ Line 73: / Line 73: @@
 * 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.
+* 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.
 * Backup the server files and database.

@@ Line 9: / Line 9: @@
 = The Tarball =
-* Make sure you update history file in docs with version and release date (and readme in root directory if needed)
+* Make sure you update history, install.html, changes.html, themevars.html files in docs (both English and Japanese) with the latest info about the 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.properties
 * Confirm git is installed on server that install package is being built on so the "changed-files" file gets updated properly

@@ Line 40: / Line 40: @@
 == glnet_curve Theme ==
-* 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.
+* 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 as users cannot change themes.
 ** 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.

@@ Line 20: / Line 20: @@
 ** '''Make sure no extra files exist as they will get included in the package. This includes db-config.php, siteconfig.php and any images and cached files.''' Best way to do this is delete the .gitignore file and then check for any new files.
 ** 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).
+** Confirm latest repository. Note: no old compressed install packages will note 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

@@ Line 29: / Line 29: @@
 *** '''IMPORTANT:''' Make sure to tag the release after you have committed the change-files file into the repository as we want these changes included as part of the version
 * Visit Geeklog.net
-** Add the new release to the downloads plugin
+** 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

@@ Line 27: / Line 27: @@
 ** 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)
-*** Make sure to tag the release after you have committed the change-files file into the repository as we want these changes included as part of the version
+*** '''IMPORTANT:''' Make sure to tag the release after you have committed the change-files file into the repository as we want these changes included as part of the version
 * Visit Geeklog.net
 ** Add the new release to the downloads plugin

← Older revision		Revision as of 16:47, 15 November 2019
Line 35:		Line 35:

	= Updating geeklog.net =		= Updating geeklog.net =
−
−	* '''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:		The following files need special handling when updating geeklog.net: