So why not lots of little releases? Leave the router for 1.2, or 1.15, or whenever its done. Just have one minor release for every little feature that brings us closer to rails. I'd much rather my migration path be of small steps, at a pace of my choosing. Have 1.1 be something small, with a short doc on "Here's the one thing you need to do to migrate an app from 1.0 to 1.1". I'd much rather that, then have 1.1 be a huge release, with 5 things I have to fix in my app right away to be able to use it. Then at least for the people that would prefer something like that, they can migrate directly from 1.0 to 1.5, on their own schedule.
Personally, I've just been following merb on github, and merging it in occasionally. Just my two cents. Paul On Jun 30, 11:13 am, Matt Aimonetti <[email protected]> wrote: > 1.0.12 got > pushed:http://yehudakatz.com/2009/06/30/merb-vulnerability-fix-1-0-12/ and we > are > working on 1.0.13 with some bug fixes I mentioned earlier. > Regarding the router, the best thing to do is to ask Carl. But as we > explained we are anyway waiting for the Rails router to be in place so we > can do an easy migration for Rails3. > > - Matt > > On Tue, Jun 30, 2009 at 8:47 AM, SoftMind <[email protected]>wrote: > > > > > Hi, > > > I would also like to go as per Matt's plans as discussed on his blog. > > > My +1 for old plans. > > > BTW... How far we are now from New Router? > > > Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
