Following the recent release of 0.10.3, we got a handful of bug reports that we wanted to address in a quick follow up release. This release is primarily composed of several important bug fixes and also improved YARD documentation coverage. Anyone using 0.10.X is recommended to upgrade to this release ASAP. Full details for this release are below.

We have also subsequently released one more minor fix in 0.10.5.

This month and the next is a great time for the Sinatra community at large. Sinatra 1.3 has been released with a lot of exciting changes. Alongside the official release, the sinatra-contrib project is also slowly maturing and will be semi-officially supported by the Sinatra team. The sinatra-recipes resource is a great reference to using components with Sinatra. In addition, Kyle Drake has come along and released sinatra-synchrony which allows for evented concurrent Sinatra applications with almost no code changes and no callbacks.

Thankfully, because Padrino is just Sinatra at its core, our framework and our users can benefit from all the great things being introduced recently for Sinatra. Today we have pushed our Padrino 0.10.3 release which contains a lot of major updates. 0.10.3 upgrades our core to Sinatra 1.3, upgrades our entire test suite to minitest, and upgrades our entire source code documentation to YARD. We have also been hard at work fixing bugs, upgrading our logger, and improving compatibility with JRuby and Rubinius wherever possible. There is also a deprecation you should be aware of in regards to rack-flash. Details for this release are below.

Just about 1 month ago, we released 0.10.1 which had several important bug fixes after our major 0.10.0 release. Today we are releasing 0.10.2 which continues in this tradition and provides a bunch more fixes that were reported since the last release. We sincerely appreciate everyone opening issues and sending us pull requests on Github. Our framework wouldn’t be half as solid without your contributions.

This release of 0.10.2 marks the beginning of our usage of TravisCI, major route reloading fixes, and a slew of bug fixes for the mailer, renderer, helpers, generators and more. We have also upgraded and locked to ActiveSupport 3.1. If you are using 0.10.1 and having trouble with the reloader, please upgrade to 0.10.2! Details for this release are below.

On July 8th, we released Padrino 0.10.0 which was the biggest release in a series of releases that are paving the way towards a 1.0 version. Fortunately, the release was well received without many serious issues cropping up during the upgrade process from 0.9.X.

Today, we are releasing 0.10.1 which is mostly a cleanup and bug fix release. Originally, we were hoping for this release to align with Sinatra 1.3 but that will likely happen in the next release now. This release adds a new mongo adapter for padrino-cache, applies some important fixes to routing, cleans up our translation files and has several compatibility and bug fixes reported since our last version. Details for this release are below.

Roughly a month has went by since our last release and there have been several developments since. Today, we are release our first minor point release in a while because we have introduced a breaking change to the way Padrino loads our rendering module.

This 0.10.0 release brings a couple new features such as enhanced route filter support, significantly faster routing engine, full compatibility with Rubinius and JRuby, bug fixes and several other improvements. The next releases coming in the pipline are 0.10.1 (for Sinatra 1.3), 0.10.2 (for AS 3.1) and then a release candidate for our 1.0 release barring any major complications. Details for this release are below.

Today we are releasing Padrino 0.9.29, the latest in a series of stability and bug fix releases designed to bring us closer to the 0.10.0 release coinciding with the release of Sinatra 1.3! This release has several essential bug and compatibility fixes that ensure developers working with Padrino have a smooth experience. This release also might require a few changes due to a tweak in how session enabling works explained below.

The biggest changes are significant speed enhancements with our routing system, a complete rewrite of our development reloader, general core cleanup and Rake 0.9 and JRuby compatibility fixes. Read below for more details.

Today we released another minor, iterative point release that addresses a few issues including development reloader hanging, couch_rest compatibility, mongoid system_timer deps, and easier Rakefile generation. For more details see the rest of this post. This release should not have any breaking changes whatsoever, so please upgrade as soon as you can.

Stay tuned for 0.9.29 and then the big 0.10.0 release coinciding with the release of Sinatra 1.3.

EuRuKo is great fun. It would be even more fun with more Padrino action, so let’s meet up!

Today, we released a new version of Padrino bringing us to 0.9.27. This release is only a week after our last hotfix release because we wanted to keep up the speed as we approach our 0.10.0 release that will coincide with the Sinatra 1.3 release.

We have also significantly improved our release processes as we approach 1.0 and now the continuous integration measures we put in place run all of our tests on every ruby version, a set of elaborate integration tests as well as full web benchmarks to measure our requests per second versus other ruby frameworks.

This release is primarily compatibility and bug fixes but also contains a few new features involving project-wide settings, reverse route recognition, and offline and test generation updates. Details of the features and fixes are below.

If you want to hear more about Padrino, a podcast was recently released on Rubiverse.

We recently released 0.9.25 which was a milestone release with many significant improvements. Unfortunately, we let a few serious bugs slip into the release as well, so a hotfix release is required.

Before going into the fixes, just want to also preface with the fact that we are taking steps to make sure future releases are better tesed. First, we used to have a CI server but the server was no longer available so we have setup a new Hudson CI server to guarantee that a release works on a variety of ruby versions and platforms. Second, we are going to do a better job of testing edge releases on our applications before released. It is important to us that each release is rock-solid before we push that out to rubygems.

A breakdown of the details of this hotfix release is in the details.