Speaking on behalf of Gin [1], I'd really like a release ASAP. I've been holding off finalizing a 1.0 of Gin because we currently depend on prerelease Guice 2.0 (and we depend on the much changed SPI).
So I'd personally try to argue for releasing the major architectural changes soon and improving things on the edges on a quick followup. -brian [1] Gin provides Guice injection for client-side GWT code. See http://code.google.com/p/google-gin for details. On Jan 5, 6:40 pm, "Dhanji R. Prasanna" <[email protected]> wrote: > My opinion: > I don't think there's a rush. We should nail everything down nicely > first, it is a pretty big release after all. I think as far as OSS > goes we're doing well by supporting trunk and patching it regularly > and keeping it healthy. For all intents and purposes we're releasing > minor and often. > > Remember there's weirdness with the struts2 plugin to be fixed too > (IMO we should dump it altogether...). > > I can certainly finish all of outstanding Servlet issues in less than > 2 weeks, but I don't think we should bow to pressure from users =( > > Dhanji. > > On Tue, Jan 6, 2009 at 1:28 PM, [email protected] <[email protected]> wrote: > > > I'd like to release Guice 2.0 as soon as possible. Here's what's > > holding it up: > > * Servlets. I'll wanna run through Dhanji's latest code, which allows > > you to configure servlets using Java (rather than XML). There's some > > feature requests and issues in our tracker on this. > > * FinalizableReferenceQueue Leaks. My preference is to neuter > > ReferenceCache for now, which will prevent a leak in J2EE servers. The > > only real downside is that it makes our code uglier, so I think it's a > > net win. We can implement a better solution later. > > * Documentation. I'm writing lots for our new docreader site. Most > > recently I wrote a new Motivation[1] page, which reformulates the > > first half of Bob's OOPSLA presentation into an introduction as to > > what Guice does. This is the first page in the new 2.0 user's guide, > > which will be a streamlined version of v1, plus new features. The new > > guide probably won't optional injection or struts 2, for example. But > > because of the way that the docreader site is integrated, that stuff > > is just a click away. > > > What's your must-haves for Guice 2? Do you think we've got a hope of > > releasing it within two weeks? > > > I'm anxious to get the release out just 'cause I think it's already a > > big improvement over v1. If I were doing it again, I think I'd prefer > > to have several smaller releases than this big-bang release. The big > > bang is kinda stressful (it has to be perfect) and it means also we're > > withholding features from our beloved users. > > > Thanks, > > Jesse > > > [1]http://code.google.com/p/google-guice/wiki/Motivation --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice-dev" 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/google-guice-dev?hl=en -~----------~----~----~----~------~----~------~--~---
