Yehuda, I have thought of one thing that caused me trouble the other day. Take for example, having a filter for auth like: before :ensure_authenticated
Examples presume you would have this in places you want auth and not have anything in places you don't require it. I do the inverse. I have this before filter in my abstract Application class and opt out of it in places that do not require auth. This is when found the problem. skip_before doesn't allow me to pass options, so I can't write: skip_before :ensure_authenticated, :only => [:index, :about, :contact] thanks, Jon On Nov 7, 12:05 am, "Yehuda Katz" <[EMAIL PROTECTED]> wrote: > On Thu, Nov 6, 2008 at 9:44 AM, Jon Hancock <[EMAIL PROTECTED]> wrote: > > > Yehuda, > > You can release 1.0 if you and those that want you to say so. But I > > would vote to keep things in RC mode for a month or so. This thing > > moves way too fast for non-core app devs to test and work through > > enough use cases to know if things are stable. Merb has changed a lot > > in the last 2 months. This hardly gives people time to work through > > things. > > > Your post I'm just replying to talks about how the install tasks are > > still half-baked. Personally, I gave up on thor weeks ago until the > > tasks are comprehensive and basic use case docs matures. > > I don't consider the thor tasks half-baked. I consider some of them to be > non-viable. The remaining tasks seem to work very well; the confusion is > about parts of the API that didn't work very well to begin with and will be > removed before the release. > > > Every open source project has its own meaning of beta and what 1.0 > > means. So if merb core devs wants to label what you have now 1.0 and > > pop some champagne, go ahead, you guys deserve to celebrate!! > > Why thank you sir. > > > My only concern is that once enough people do use it (and I think that > > is part of your drive to label it 1.0, isn't it? to get a larger > > audience comfortable with using it? because early adopters don't care > > what the version label is), we will find use cases for adjusting the > > API or refactoring to be accessible to newbs. And then the story > > becomes, uh, well "the API was frozen ;) sorry, now you have to wait > > for much longer release cycles.,,or live on edge...or start monkey > > patching." > > We've been pretty frozen on API since RC1, and I'm very confident freezing > the API now. The remaining issues, to the extent that they exist, are more > in the realm of bugs that could be resolved without API breakage. If we wait > another month, we'll still not have the adoption we need (in your view) to > discover these changes, and another month has passed. > > Our goal is to release 2.0 (a potentially breaking release) next summer, so > I wouldn't worry about insanely long release cycles. > > > Anyway, as always, thanks for a great product1!! For all the teeth > > cutting, I'm still happy to have merb. > > Again, thanks! > > > > > > > Jon > > > On Nov 6, 9:43 pm, "Yehuda Katz" <[EMAIL PROTECTED]> wrote: > > > A few things: > > > First, Merb stack will always be installing DM 0.9.6, which is the latest > > > DM, even on edge. The point of the stack is to install a known-working > > set > > > of gems, which cannot be said about edge DM. It's easy enough to modify > > the > > > generated output to use 0.9.7 if you want it. > > > > Second, at this point we're not really recommending the use of > > > merb:dependencies:install because we haven't worked the kinks out (and > > > probably won't before 1.0). Instead, use merb:gem:install, which you can > > use > > > to install individual gems. You can do merb:gem:install merb-more to get > > the > > > merb stack minus DM. merb:dependencies:install should also work with a > > > dependencies.yml file (the difficulty with trying to install out of your > > > init.rb is that you need to be able to fully start your app first, which > > you > > > can't do without having the deps; i.e. a catch-22). > > > > Does all of that make sense? Do you still have any questions? > > > > -- Yehuda > > > > On Thu, Nov 6, 2008 at 8:16 AM, Martin Gamsjaeger <[EMAIL PROTECTED] > > >wrote: > > > > > Hey, > > > > > It seems that current edge (0.9.14 from edge.merbivore.com) suffers > > > > from a regression because i thought i remember that this was already > > > > fixed before? > > > > >http://www.pastie.org/308689 > > > > > This shouldn't happen. The generated dm_gems_version in > > > > config/dependencies.rb should be 0.9.7. > > > > > Also (after fixing dm_gems_version), when i do a > > > > > thor merb:dependencies:install > > > > > it will bundle merb-0.9.13 which in turn leads to ./bin/merb -i saying > > > > > ~ Loaded DEVELOPMENT Environment... > > > > ~ FATAL: The gem merb-action-args (= 0.9.14, runtime), [] was not > > found > > > > ~ FATAL: The file merb-action-args was not found > > > > > because in config/dependencies.rb it says merb_gems_version = "0.9.14" > > > > > I would gladly offer a patch, but I'm really rather confused against > > > > which branch that should be. With all the branches and forks, I'm kind > > > > of lost as to what exactly is considered merb edge. If this is already > > > > fixed somewhere, I'm happy to wait until this makes it into 1.0. If > > > > not, i would vote for *special* care about merb-gen (the dependencies > > > > it generates) and thor bundling (to match these dependencies) > > > > > cheers > > > > snusnu > > > > > On Thu, Nov 6, 2008 at 8:58 AM, Yehuda Katz <[EMAIL PROTECTED]> wrote: > > > > > Hey guys, > > > > > We have one full day before Merb 1.0 final is released. In light of > > that, > > > > > I'm making a call for remaining bugs that you consider urgently > > required > > > > > before 1.0, and that can be fixed in the short time remaining. > > > > > We'll probably release a few 1.0.x releases to continue to solidify > > the > > > > > final release as bug reports come streaming in, but please limit your > > > > > replies to this thread to urgent problems that can be fixed quickly. > > > > > Thanks! > > > > > > -- > > > > > Yehuda Katz > > > > > Developer | Engine Yard > > > > > (ph) 718.877.1325 > > > > -- > > > Yehuda Katz > > > Developer | Engine Yard > > > (ph) 718.877.1325 > > -- > Yehuda Katz > Developer | Engine Yard > (ph) 718.877.1325 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
