Currently the bugs have been assigned to me on Lighthouse, but I admit I've been slacking on this regard. I'll try to make a bigger push to get the 1.1 bugs organized and reviewed in the next couple weeks.
ojak, if you're interested I'd love your help on this. I'll email you my gtalk info and we can work together to get some of the many low hanging fruit merb bugs resolved. Anyone else interested in helping, just email me. Thanks On Jul 1, 1:19 am, ojak <[email protected]> wrote: > Matt, > > You mentioned that Merb 1.1 has been ready for several weeks, but > there are still over 70 tickets in Lighthouse for it, some of which > are pretty critical. If 1.1 is in fact ready to go, would it be > possible for someone with access to clean up the Lighthouse tickets so > we can better understand the progress? I think that would greatly > help. > > Thanks! > > On Jun 29, 1:35 am, Matt Aimonetti <[email protected]> wrote: > > > > > See my comments below: > > > On Sat, Jun 27, 2009 at 8:34 PM, MyMerb <[email protected]> wrote: > > > > Hi, > > > > I would like to ask this question to all Merb developers specially ... > > > (1) Yehuda and (2) Matt from Merb Core Team. > > > > Pl. be frank and honest. > > > > Question 1:- Is Merb 1.1 really coming, or plans are dropped > > > Merb 1.1 has been almost ready for a few weeks now. I was waiting for Carl's > > new router but as Yehuda explained things are not simple and maybe we should > > consider releasing 1.1 without the new router. > > > > Question 2:- Will the Merb progress die after Rails 3.0 > > > The current core team won't be working on new features since we are working > > on Rails 3.0, but Merb will still be supported as will Rails 2.x be. > > > > Question:- Why there are no updates on Merb Information and Merb > > > Book..? > > > Mainly because we've all been really busy, that's certainly not a good > > excuse. I'm personally really busy at work, decided to spend more time with > > my family and also got involved in MacRuby on top of the Rails team. > > > We'll make an effort to communication better. > > > > Question:- Is Merb Core Team willing, All Merb developers should shift > > > to Rails 2.3.2 as soon as possible...? > > > I'd not recommend to switch from Merb to Rails 2.3.2, Merb is very stable > > and used by a lot of companies such as wikimedia, adobe, EY, many of my > > clients and many more. You should switch to Rails3 when it will be ready > > tho. > > > > Question:- Which great asests of Merb are coming in Rails 3.0..? > > > There are a lot of posts about that, check the latest rails conf talks. > > > > Finally... > > > > Question:- Should we stick to Merb or move away to Rails as soon as > > > possible..? > > > See previous answer above. > > > Regarding migration path... Since Rails3 isn't ready, there isn't much to > > migrate to. Engine Yard put Yehuda and Carl to work full time on Rails and I > > hope they will get them to work on the migration. My guess is that it will > > happen since they will need this migration for themselves (solo/flex). > > > Note that I totally understand your frustration. You got used to a > > bi-monthly release cycle and 1.1 still isn't out. I'm myself also a bit sad > > to notice that so little effort put on Rails is enriching Merb yet. However, > > I do believe things will change once Rails3 will be more mature and we will > > be able to start exchanging code. > > > - Matt > > > p.s: remember that Merb is a Free Open Source project and that it won't die. > > A new team is still free to keep on working on the framework if they see > > that's the way it should be. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
