Padrino 0.9.15 adds in a few new features. You can now use templates to generate entire padrino projects or use plugins that will easily integrate libraries and other components into your padrino project. In addition to fixes, this version adds new translations as well as components from stylesheets, renders, and orms!

Padrino 0.9.14 is another small bugfix release which solves a few common problems revealed with the deprecation of mount_core. This is not at all a release which requires any changes to your app. The details of the bugs fixed are listed in the full post.

Welcome back to Padrino weekly. This week is certainly dominated by football, but I hope we’ll get over it. I’ll keep this short so you can go back to watching whichever game you’re watching.

Padrino Weekly will be a weekly summary of the activities in the Padrino ecosystem. The intention is to give all interested users a quick and easy way to follow the efforts of the core developers as well as the community as whole. We’ll try and provide pointers to important events, interesting discussions as well as contributions in the last or upcoming week. We’ll also point to long term developments that might be of interest.

Following the release of 0.9.11 yesterday there were a few unresolved issues that were quickly discovered. In order to create the smoothest experience possible for Padrino users, we decided that these bugs warranted a new release ahead of schedule. So, today we have released 0.9.13 (and 0.9.12) with a few bug fixes and a deprecation of the mount_core method. Read on to get the full rundown.

thechangelog is a weekly podcast hosted by Adam and Wynn that discusses “what’s fresh and new in open source”. Two of the core Padrino team members, Nathan and Arthur, recently had an opportunity to chat on air when Adam and Wynn decided to devote an entire episode to Padrino! The podcast runs for about 32 minutes and includes a nice discussion about Rack, Middleware, Sinatra and Padrino. Read the full blog post to listen to the interview!

Today the Padrino team released the new version 0.9.11. This version contains a number of new features and a lot of bug fixes. The features and fixes include a new mailer, improved routing support, core refactorings, enhanced test coverage, new language translations, and much more.

Also worth noting is that this version contains a few backwards incompatible changes to the API from 0.9.10. These changes are to help stabilize the Padrino API towards a 1.0 release and generally improve the consistency of our framework.

This post will guide you through the specific changes that are needed to fix compatibility for 0.9.11 and also explain in much more detail what has changed in this release.

The Padrino team is excited to welcome aboard three new core members to help us make Padrino even better towards a 1.0 release!

These three members bring a great deal of experience and talent to our group and will definitely push forward the power of Padrino in the next upcoming versions.

The three new core members are Florian Gilcher, Joshua Hull and Lori Holden and they will all start right away contributing towards Padrino.

Read the full post to learn more about our new members and how they plan to help improve Padrino.

Our team is pleased to announce the 0.9.10 release of the Padrino Framework!

We have been working hard on Padrino since our first ‘public’ announcement and we have gotten a lot of amazing feedback and suggestions! This new release contains three major types of changes:

1) Performance Optimizations
2) Added Features
3) Bug Fixes

In the full post below, we will take you through a detailed tour of the biggest changes in this release (for a more compact view, see our changelog). Also, the full post contains benchmarks comparing Padrino to other popular ruby frameworks!

Over the last week, we have taken the first steps towards showing Padrino to a larger audience of Ruby and Sinatra fans. Our team and other developers have gotten around to announcing Padrino on RubyInside, Rubyflow, the Ruby5 Podcast, Hacker News, the Sinatra Google Group, among other sources.

The chatter on twitter and the fact that Padrino has become a most watched ruby repo this month on Github shows this little framework is gaining an audience. Thus far, our team has been very pleased with the feedback that we have gotten even already after the various announcements. The response has been overwhelmingly positive and constructive and we wanted to thank everyone for taking the time to explore what Padrino is all about!

At the same time, there have been a couple questions that have popped up along with some valid criticisms and/or confusion as to what the Padrino framework is all about. I would like to take this blog post as an opportunity to address many of these concerns as well as talk a little bit about the future of Padrino.