Welcome to Geeklog Thursday, January 19 2017 @ 03:40 am EST

Geeklog's Next Release and the PHP Version Requirement

  • Contributed by:
  • Views: 870
Geeklog

As we get ready for the next version of Geeklog (either version 2.1.2 or 2.2.0) support for PHP 7 is being discussed. The current version of Geeklog (2.1.1) requires at least PHP 5.2.0. The code for the next version of Geeklog and the core plugins supports PHP 7.0.x but Pear and a few other 3rd party libraries included with Geeklog do not. To upgrade these libraries so they support PHP 7 we must raise the minimum PHP version required to run Geeklog to 5.6.x.

A poll has been created so we can find out from the community what PHP version they are currently using and what version they can upgrade too. This will help us decide better what the new minimum version well be and how important PHP 7 is to the community.

To give you an ideal on the state of the development of PHP itself, support for PHP version 5.3.x and 5.4.x has been out of development for a while now and PHP 5.5.x is currently only receiving security fixes to the end of the year. Support for PHP version 5.6.x will continue to receive fixes until the end of 2018.

To help us decide what version of PHP should be a requirement for Geeklog please participate in our poll:

PHP Support for the next version of Geeklog

Which PHP version are you on?

  •  PHP 5.2.x
  •  PHP 5.3.x
  •  PHP 5.4.x
  •  PHP 5.5.x
  •  PHP 5.6.x
  •  PHP 7.0.x
  •  Don't know / other
This poll has 2 more questions.
Results
Other polls | 48 voters | 0 comments

Geeklog on Gitter

  • Contributed by:
  • Views: 576
Geeklog

We have recently opened a Geeklog room on Gitter as a replacement for IRC. Gitter allows developers to chat together online as a group, or in private conversations one on one. Gitter integrates well with Github (which Geeklog recently swithed too)  including the repositories, issues and activities. You can access Gitter via their website and apps (iOS and Android).

The Geeklog room on Gitter is open to the public for viewing but you will need to create a free account if you wish to participate, ask a question or answer someone's query. If you are an aspiring programmer or seasoned developer and wish to particpate in developing Geeklog or coding a plugin, come and introduce yourself.

Geeklog has Switched to GitHub

  • Contributed by:
  • Views: 2,235
Geeklog

Back in September of 2008 Geeklog made the switch from CVS to Mercurial to take advantage of a distributed version control system. Geeklog had used CVS for about 7 years. Source control has kept improving and after another 7 years The Geeklog Team has decided to move from using Mercurial to Git, and to using GitHub as our web-based Git repository hosting service.

This change really only affects the developers of Geeklog. Normal web masters who use the Geeklog CMS will not notice any changes.

We decided on the change since GitHub offers all of the features our older setup had plus many more and, it is one of the largest source hosting services in the world. It also means we don't have to worry about maintaining our old systems and we can concentrate more on coding. GitHub offers many social networking type features along with the ability to track issues, access control, teams, fork projects, wikis, and task management. Plus currently a large number of Geeklog Plugins use GitHub as well.

The new Geeklog CMS and related code repositories can be found at the GitHub Geeklog Core Organization.

The Geeklog Team also have decided to switch from using our current Bug Tracker (called Mantis) to the Issue tracker which GitHub provides. We have updated the links on Geeklog.net and the Geeklog Wiki to reflect these changes. We have imported all the open and closed bug reports and feature request from our old Bug Tracker to GitHub. Some information we could not automatically import so the issues in the new tracker need some updating which we will get to in time. Information which needs updating includes labels, milestones (which version it is for) and descriptions. For this reason the old Mantis Bug Tracker will still be accessible but, please do not add any new information to it.

For all new bug reports and feature requests, please submit them to the new Geeklog Issues Tracker.