Fork 2.3.0 released

  • Written by Matthias Mullie on Tuesday 7 June 2011
  • 3 comments

Today we released Fork 2.3.0.
Keep in mind that this release is not 100% backwards compatible, hence the new major release. You can also follow Fork on github.

Changelog

Bugfixes

  • When the metafields are disabled we don't have any values in the POST. When an error occurs in the other fields of the form the meta-fields would be cleared. As reported on http://forkcms.lighthouseapp.com/projects/61890/tickets/164.
  • Moving pages for a non-active language failed, as reported on http://forkcms.lighthouseapp.com/projects/61890/tickets/163.

Improvements

  • Upgraded to jQuery 1.6.1
  • Upgraded to jQuery UI 1.8.13
  • Upgraded TinyMCE to 3.4.2

Comments

Wolf

Wolf wrote 12 years ago

x.x.x releases are for bugfixes

x.x releases are for features within the current version

x releases are for major new releases

Releasing bugfixes as x.x releases is confusing.

Tijs

Tijs wrote 12 years ago

@Wolf:

x.x.x are indeed bugfix-releases

x.x are for releases with non-backwardscompatibel features.

jQuery 1.6.1 isn't compatible with the 1.4 version we used before and would break stuff that was build on 2.2.x.

Per

Per wrote 12 years ago

Personally, prefer the major.minor.patch scheme as explained in "The art of unix programming":

http://www.catb.org/~esr/writings/taoup/html/ch19s02.html#naming

"The convention for distinguishing major from minor release is simple: you increment the patch level for fixes or minor features, the minor version number for compatible new features, and the major version number when you make incompatible changes."

But that's maybe because I'm an old fart ;-)

Anyways, from that same chapter:

"But respect local conventions where appropriate."

It would be cool though if we could just have 'the latest' version :)