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
I wouldn''t bother with reducing the revision number. If anything having weirdly high ones makes the project seem more alive and active. Is the minor number even functionally useful here? Maybe we should ditch that and just keep major as a "look! An increment! Heaps cool stuff must have happened!" unless google chrome has ruined new major numbers for everyone anyway. ? Jenna On 02/10/2011, at 10:43 PM, Magnus Holm <judofyr at gmail.com> wrote:> 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 at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list
On Sun, Oct 2, 2011 at 14:26, Jenna Fox <a at creativepony.com> wrote:> I wouldn''t bother with reducing the revision number. If anything > having weirdly high ones makes the project seem more alive and active. > Is the minor number even functionally useful here? Maybe we should > ditch that and just keep major as a "look! An increment! Heaps cool > stuff must have happened!" unless google chrome has ruined new major > numbers for everyone anyway.Well, it''s useful for computability reasons. Every app created on 2.x should work on 2.x+n with minimal required changes.
True that. Meanwhile, have you guys seen <http://twitter.github.com/bootstrap/> ? It looks pretty nice, and I imagine something like that could be pretty powerful if deeply integrated with a version of markaby, as a ''ui toolkit for the web'' sort of thing - a nice sensible clean default style for quickly prototyping ideas, and teaching beginners the concepts of the web. ? Jenna On 03/10/2011, at 8:47 PM, Magnus Holm wrote:> On Sun, Oct 2, 2011 at 14:26, Jenna Fox <a at creativepony.com> wrote: >> I wouldn''t bother with reducing the revision number. If anything >> having weirdly high ones makes the project seem more alive and active. >> Is the minor number even functionally useful here? Maybe we should >> ditch that and just keep major as a "look! An increment! Heaps cool >> stuff must have happened!" unless google chrome has ruined new major >> numbers for everyone anyway. > > Well, it''s useful for computability reasons. Every app created on 2.x > should work on 2.x+n with minimal required changes. > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20111003/47941b18/attachment.html>
Personally I hate it. It''s like <table border=2> and <font size=7> once again, except this time camouflaged as CSS classes. The only good things in there are either styled pretty much the same way by default (like, say, headers), or require a line of code (@basefont, layouts). -- Matma Rex 2011/10/3 Jenna Fox <a at creativepony.com>:> Meanwhile, have you guys seen <http://twitter.github.com/bootstrap/> ? It > looks pretty nice, and I imagine something like that could be pretty > powerful if deeply integrated with a version of markaby, as a ''ui toolkit > for the web'' sort of thing - a nice sensible clean default style for quickly > prototyping ideas, and teaching beginners the concepts of the web. >
Oh right, but you can use that LESS thing I think to compile the bootstrap properties in to your regular CSS, so you keep using good quality selectors, and bootstrap essentially augments your CSS with useful macros. Another way to do it is to define markaby helpers for each kind of thing, so you can still just go change one small piece of code to restyle the whole site''s whizlebobs. ? Jenna On 04/10/2011, at 3:07 AM, "Bartosz Dziewo?ski" <matma.rex at gmail.com> wrote:> Personally I hate it. It''s like <table border=2> and <font size=7> > once again, except this time camouflaged as CSS classes. The only good > things in there are either styled pretty much the same way by default > (like, say, headers), or require a line of code (@basefont, layouts). > > -- Matma Rex > > > > 2011/10/3 Jenna Fox <a at creativepony.com>: >> Meanwhile, have you guys seen <http://twitter.github.com/bootstrap/> ? It >> looks pretty nice, and I imagine something like that could be pretty >> powerful if deeply integrated with a version of markaby, as a ''ui toolkit >> for the web'' sort of thing - a nice sensible clean default style for quickly >> prototyping ideas, and teaching beginners the concepts of the web. >> > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list