For 2.2 we won't support 1.8 for development/test, since we depend on gem's that need >= 1.9. But for production it would be nice to support 1.8.7 for 2.2. For 2.3, we drop the support and we can use 1.9.3-isms like tag: "starred" instead of :tag => "starred"
Reinier > -----Oorspronkelijk bericht----- > Van: tracks...@googlegroups.com [mailto:tracks...@googlegroups.com] > Namens Matt Rogers > Verzonden: dinsdag 4 september 2012 5:23 > Aan: tracks...@googlegroups.com > CC: tracks-discuss@lists.rousette.org.uk > Onderwerp: Re: [Tracks-discuss] tracks cache-enabled > > On Sun, Sep 2, 2012 at 8:28 AM, Reinier Balt <lrb...@gmail.com> wrote: > >> > Hi all, > >> > > >> > I've tried the new cache-digests gem to easy add caching to Tracks. > >> > (I had to clone the gem to enable it running on ruby 1.8.7) > >> > >> Perhaps it would just be better to drop 1.8 support for master > >> instead? I don't think we need the maintenance burden at this point. > >> The majority of the ruby/rails community has also made the switch to > >> 1.9 > > > > I like to do 2.2 with 1.8.7 support because my own server (fc 15) only > > supports 1.8.7. So this is completely selfish :-) But I'll upgrade my > > server at the end of the year and my dependency is gone. > > > > I used to run an Tracks on an FC 15 server as well. But once Tracks was > compatible with 1.9.x, I just set up RVM and used 1.9.x via that mechanism. > I'd really love to get Tracks up to the latest recommendation for our software > stack ASAP, preferably with 2.2. It decreases the amount of work we have to > do and other stuff we have to maintain ourselves (e.g. your cache_digests > gem). I'm also ok with doing one last release that's 1.8.x compatible too, so > my main passion around this is saving ourselves time and effort. :) > > > > > BTW, I do not see a lot of tickets for 2.2, so we could go to 2.2RC to > > get more people testing. But I'd like some feedback on the recent > > caching changes. > > > > Do the tests still pass? If so, let's just make an RC and be done with it. The > tests should tell us everything we need to know. > > >> > N.B. This message is cross-posted to the old and new mailing list. > >> > This list will be closed shortly. The new list is at > >> > > >> > https://groups.google.com/forum/?hl=en&fromgroups=#!forum/tracksapp > >> > > >> > >> Please send out a separate announcement for this. This is too > >> important to be buried here, IMO > > > > True, but I leave that to bsag to officially kill the original list > > :-) > > > > What purpose does waiting serve to kill the old list? Let's kill the old list > ourselves - as a community - by just never posting there anymore and then > when bsag's hosting goes away, then the list dies. > Problem solved - right? - or am I missing something? > > > Reinier > > > > Thanks > -- > Matt > > -- > You received this message because you are subscribed to the Google Groups > "TracksApp" group. > To post to this group, send email to tracks...@googlegroups.com. > To unsubscribe from this group, send email to > tracksapp+unsubscr...@googlegroups.com. > Visit this group at http://groups.google.com/group/tracksapp?hl=en. > _______________________________________________ Tracks-discuss mailing list Tracks-discuss@lists.rousette.org.uk http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
