Meta Bates

If you haven’t noticed by now, I tend to release smaller releases more often. I know there isn’t much precedent for that as Mack has only been out a week, and there’s only been three releases, but I can assure you, it’s a sign of things to come.

I feel that at this stage in a code’s life cycle, it benefits from getting out into the wild sooner, rather then later. Sure, I could bulk up features and bug fixes and do big ‘wow’ factor releases, but why should I sit on a cool feature or an important bug fix simply so I can have a bit of ‘wow’? Why not let people start to enjoy those new features, and give me important feedback earlier?

I’m sure as the code tree grows and people start really using Mack, things may slow down a bit. When there are more developers then just myself, things will definitely slow down a pace, but until then, I just don’t see the point in holding back.

When I have something cool and ready to go, I’m going to release it. You don’t have to upgrade your Mack environment if you don’t want to, you can if you want. If you would prefer to ‘bulk’ them up yourself, then that’s entirely up to you. Like I’ve said before, Mack is trying to be as non-opinionated as it can be. That includes how you update your system.

Anyway, I just thought I would share a bit of how things will be handled going forward. I hope that’s fine with you.

Have a good weekend.

Please allow for mirror prorogation.  Thanks to Matt Todd for finding the first official Mack bug! Strangely enough, I actually welcome people finding bugs in Mack. It only serves to make it a better framework.

If you find a bug, please head on over to RubyForge and submit a ticket for it, and I’ll do my best to turn it around as quick as possible.

Changelog:

• gem: thin 0.7.0

• gem: cachetastic 1.3.1

• Fixed 18487: #convert_security_of_methods ignores new_level param

Mack has only been around for a few days, and people are already started to download it and link to. Yippie!

http://maraby.org/post/27611841

http://sness.blogspot.com/2008/02/mack.html

http://anarchaia.org/archive/2008/02/28.html

http://yogindar.blogspot.com/2008/02/ruby-web-application-framework-mack.html

Get it while it’s hot! Of course, you’ll probably want to wait a bit for it to propagate to all the gem mirrors. If you really can’t wait, you can find it here.

$ sudo gem install mack

From the CHANGELOG:

• rake generate:<generator_name>

• rake generate:plugin – will generate the stub of a plugin in the vendor/plugins directory.

• rake dump:config – prints out the configuration information for the specified environment.

• redirect_to now takes an optional Hash as a second parameter, instead of a fixnum.

• redirect_to will now do server side redirects if passed :server_side => true as part of the optional second argument Hash.

• plugin in support. plugins get loaded before the ‘app’ directory. each plugins ‘lib’ directory is added to the global load path and then each plugins ‘init.rb’ file is called, which is responsible for loading the necessary files. The ‘lib’ directories are finally removed from the global load path.

• renamed initialize directory to initialization. moved logging, orm_support, and plugins to a subfolder called initializers.

Last night the first public release of Mack was made available on RubyForge. So get it now:

$ sudo gem install mack