I'm thinking of releasing 2.1.458 which includes a few more features (better cookie support, inline templates etc), but mainly to fix some incompatibility issues with Rack. I'm not going to document the new features yet, so consider them experimental in this patch-release.
As for the version, it's currently MAJOR.MINOR.REV where REV = number of commits since the beginning. It works pretty well to use REV as a part of the version number because I can then easily throw out experimental releases to my gem server without screwing up the version number. However, from 2.2 I'm thinking of changing REV to "number of commits since previous release", simply to avoid some high revision numbers. Thoughts? Okay with a little maintenance release? Okay with some undocumented experimental features? Okay with REV? Okay with decreasing REV a bit= // Magnus Holm _______________________________________________ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
